On slower connections / machines, the Configure Rule flyout briefly shows "You have not been authorized to create any Rule types" even though user has permissions

[CoenWarmer]

Kibana version:
8.6.0

Elasticsearch version:
8.6.0

Server OS version:
n/a

Browser version:
n/a

Browser OS version:
n/a

Original install method (e.g. download page, yum, from source, etc.):
From source

Describe the bug:
When configuring a new rule, the Configure Rule flyout briefly shows "You have not been authorized to create any Rule types" even though user has permissions. This can be seen on slower connections / clusters.

Steps to reproduce:

1. Make sure you are on a slower cluster (for example, all CCS clusters exhibit this behavior)
2. Navigate to /app/observability/alerts/rules
3. Click "Create rule"
4. The flyout will appear in a loading state
5. The first loading state in the flyout will finish, showing the fields to enter the name of the rule. But a second loading state inside the flyout for a brief moment will flash the message "You have not been authorized to create any Rule types".

you-are-not-allowed.mov

Expected behavior:
The permissions message should not appear if the logged in user actually has the correct permissions to configure a rule.

The application should wait until the api call to rule_types is done loading before deciding which message to show to the user.

Screenshots (if relevant):
See screen recording above

[CoenWarmer]

The UI seems to show this message while the call to /api/alerting/rule_types is in flight.

[pmuellr]

hahahaha ... I found this yesterday, and was about to open an issue with a screen cap movie, only to find my deployment was a complete wreck and so figured it was some other problem.

Good find!