feat: service page using form components

[ElderMatt]

Also see the other PRs:

• API
• CORE

Considerations

• I have tested the changes in both light and dark mode.
• I have considered the need for new unit tests.
• I have tested the changes on a cluster.
• I have included relevant documentation updates.
• I have an approved Figma design or have reflected my changes in Figma
• I have verified that the UI/UX is consistent in major browsers (e.g., Chrome, Firefox, Safari, Edge).
• I have tested the changes for responsiveness in different screen resolutions.
• I have tested expected error states and verified that the user is presented with informative error messages.
• I have tested the feature with unusual or extreme inputs (e.g., very long strings, empty states, clicking a button multiple times quickly).

[dennisvankekem]

first pass, UI test will follow later

[dennisvankekem]

I'm missing the title and description here (domain aliases CNAME)

[dennisvankekem]

traffic management can go over 100%

[dennisvankekem]

I'm missing the service url summary next to the submit button

[dennisvankekem]

creating a service without filling in namespace returns an error instead of a form valiation error in the frontend

[dennisvankekem]

first ui pass, please see comments

[ElderMatt]

traffic management still has the 50/50 default bug

• Fixed

[ferruhcihan]

On Thursday, we worked together with @ElderMatt and @dennisvankekem and tested it, but we weren’t able to expose the services consistently.
Aside from that, the code looks good. The new components are functioning as expected, so it’s LGTM from my side.

[dennisvankekem]

well done, this was a hard one