Editor: Reorder service as resource fields

[AlitaBernachot]

Description

This PR changes the display order for the fields in the service-as-a-resource form.

• reorder fields: 1. url field 2. Layer or Process name
• add a placeholder "Process name" if WPS is selected, "Layer name" for others
• hides the url upload button and add a new one to validate new protocol submission
• url input has been updated to allow any content or custom icon in place of the orginal "upload" icon

NB. This is preparatory work for next topic (layer name suggestion), some function like handleServiceUrlChange and handleIdentifierSubmit will be improved/clarified in next ticket.

Architectural changes

None

Screenshots

NB. The upload button is hidden for now as there is a new "Link to the service" button. The upload button will be used in next PR for layer suggestion.

Quality Assurance Checklist

• Commit history is devoid of any merge commits and readable to facilitate reviews
• If new logic ⚙️ is introduced: unit tests were added
• If new user stories 🤏 are introduced: E2E tests were added
• If new UI components 🕹️ are introduced: corresponding stories in Storybook were created
• If breaking changes 🪚 are introduced: add the breaking change label
• If bugs 🐞 are fixed: add the backport <release branch> label
• The documentation website 📚 has received the love it deserves

---

[github-actions]

Affected libs: feature-editor,
Affected apps: metadata-editor,

• 🚀 Build and deploy storybook and demo on GitHub Pages
• 📦 Build and push affected docker images

[coveralls]

coverage: 81.624% (-2.4%) from 84.022%
when pulling b07515b on service-reorder-fields
into 923a1d3 on main.

[github-actions]

📷 Screenshots are here!

[cmoinier]

Thanks for this work! I've left a few comments :)

When testing, I noticed that after submitting the link, the fields stay filled (see screenshot) and the button stays focused. This is maybe not a priority, but I would expect them to cleanup/unfocus because the user might want to add another link without having to delete the previous values, WDYT? Something like the spatial extent input is doing. But on the other hand, it's not like the component was doing it before anyway, so you can decide.

[AlitaBernachot]

Thanks for your review!

When testing, I noticed that after submitting the link, the fields stay filled (see screenshot) and the button stays focused.

=> Ok fixed for all gn-ui-button.

This is maybe not a priority, but I would expect them to cleanup/unfocus because the user might want to add another link without having to delete the previous values, WDYT? Something like the spatial extent input is doing. But on the other hand, it's not like the component was doing it before anyway, so you can decide.

=> Ok i have updated the code: now we clear the identifier entry after submit. As for the url I don't know if we should remove it, maybe the user wants to add multiple layer from a same service? Tthis point should be discussed with the UX team maybe?