[dashboard] BlockedRepo UI

[geropl]

Description

This still looks... ugly, but fixes the general issue of not being able to add blocked repositories from the UI.

Related Issue(s)

Fixes #

How to test

Release Notes

NONE

Documentation

Werft options:

• /werft with-preview

[werft-gitpod-dev-com]

started the job as gitpod-build-gpl-blocked-repo-ui.1 because the annotations in the pull request description changed
(with .werft/ from main)

[geropl]

@AlexTugarev Can you maybe 10mins tomorrow and help me fix the basics for the 🛹 ? 🙏

@gtsiolis I guess you're pretty busy, but: It would be awesome if you could have a look (independent of when we merge this) and come up with a nice version - happy to implement that. ✨

[gtsiolis]

Looking at this now! 👀

[gtsiolis]

Thanks for adding this, @geropl! 🔮

Left some comments in case we'd like to address all these UX issues here or in a separate PR.

Approving to unblock merging this, but holding to let someone from the @gitpod-io/engineering-webapp to take a closer look at the code changes. 🏓

/hold

[geropl]

/unhold

I addressed as much of the suggestions as possible to still get the release train 🚆 😆

To reiterate why I think this is ok:

• this is admin functionality, so very limited audience, and not in front of (paying) users
• we should still aim high, but we also want this in prod asap, as it eases on-call 💯
• none of the trade-offs we took here do affect safety or stability (e.g., even without more validation, the regexes do no harm)
• The follow-up PR for fixing the UX issues is mandatory 🙃

[geropl]

Thank you @andrew-farries and @gtsiolis for your valuable feedback! 🙏

[gtsiolis]

Thanks @geropl! I've updated the screenshot in the PR description to reflect the changes from this PR for future reference, and opened #11463 to summarize the outstanding points mentioned in the discussions above. 🏓