View and edit SSO config

[fiskus]

• Check if there is SSO config (without fetching it) and show "individual assignment" icon button
• Show YAML editor in popup dialog. Editor is heavy, but it is lazy loaded

• Changelog entry (skip if change is not significant to end users, e.g. docs only)

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 89 lines in your changes missing coverage. Please review.

Project coverage is 38.33%. Comparing base (1953dcf) to head (aec4242).

Files	Patch %	Lines
...g/app/containers/Admin/UsersAndRoles/SsoConfig.tsx	0.00%	65 Missing and 1 partial ⚠️
...talog/app/containers/Admin/UsersAndRoles/Roles.tsx	0.00%	11 Missing ⚠️
catalog/app/utils/GraphQL/Provider.tsx	0.00%	4 Missing ⚠️
catalog/app/components/Lock/Lock.tsx	0.00%	2 Missing ⚠️
.../Admin/UsersAndRoles/gql/HasSsoConfig.generated.ts	0.00%	2 Missing ⚠️
.../Admin/UsersAndRoles/gql/SetSsoConfig.generated.ts	0.00%	2 Missing ⚠️
...ers/Admin/UsersAndRoles/gql/SsoConfig.generated.ts	0.00%	2 Missing ⚠️

Additional details and impacted files

@@                    Coverage Diff                    @@
##           role-mapping-frontend    #4072      +/-   ##
=========================================================
- Coverage                  38.43%   38.33%   -0.10%     
=========================================================
  Files                        717      718       +1     
  Lines                      33060    33045      -15     
  Branches                    4859     4878      +19     
=========================================================
- Hits                       12706    12669      -37     
- Misses                     19207    19228      +21     
- Partials                    1147     1148       +1     

Flag	Coverage Δ
api-python	90.75% <ø> (ø)
catalog	11.45% <0.00%> (-0.05%)	⬇️
lambda	89.06% <ø> (+1.09%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[nl0]

looks ok, tho i wouldn't use a separate partial query.
let's merge this into the upstream PR anyways and finish it off there,
since i feel quite confident we're shipping this one too.

[nl0]

does this handle submit errors properly? i vaguely remember i had some confusion with form errors vs submit errors -- they were under different fields and i had to check both these fields, but i don't remember which api this was, maybe form-level 🤷

[fiskus]

This is for field-level errors. And I just don't show the validation error when form hadn't submitted.
This piece of code is the same as in other TextField across app.

On the other hand, form-specific error. There I made a "shortcut" and since this form is one-field, I show the error from API directly, not from final-form.