When a rule encounters a licensing error it doesn't pick up a licensing fix automatically

[EricDavisX]

Kibana & Stack:
8.3.0-SNAPSHOT

Describe the bug:
When a Rule encounters a licensing problem it correctly shows a licensing error in Kibana, but when the license level / expiration is fixed the Rule UI does not immediately show the correction (the error banner remains).

Steps to reproduce:

1. install Kibana, create a rule and run it every minute
2. set the stack into a state with an expired license
3. in one minute check the rule and see the license problem
4. fix the expired license
5. again, wait a minute and check the rule; note that the license error is not resolved

Expected behavior:
The license error should automatically be resolved. A simple way to fix this, is to disable and then re-enable the rule, this causes it to run at which time it checks the license and appears fixed

Screenshots (if relevant):

Any additional context:
Thank you to The Observability Engineering Productivity group for finding this for us.

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[XavierM]

@mikecote did your team already talk about this in the past? we might miss some plumbing when we fix the license.

[mikecote]

@mikecote did your team already talk about this in the past? we might miss some plumbing when we fix the license.

Last we spoke, we wanted to change the message to relate it to the last time the rule ran instead of making it sound like Kibana can't run the rule. We were also thinking of giving the users the ability to re-run the rule, which will be available soon! #139848

[Zacqary]

@mikecote Reviewing this issue again, is this still a RAM issue or E&C?

[mikecote]

@mikecote Reviewing this issue again, is this still a RAM issue or E&C?

From what I recall about this issue, we have the rule in a last run of error, with a message complaining about the license. Once the user fixes the licensing, the rule hasn't run again so it still has this last run of error and the UI renders it that way.

It feels like if we were to do anything, it may be in the management UIs / UX (R&AM)?