Add workflow event providers for user lockout events by brute force protection - #51466

@robson90 - thanks for pinging me. While this looks good overall, it might need some more justification in the parent issue to add this. I already added a comment, but maybe you can make this stronger.

There is one nitbit that GitHub copilot found in the docs: The "User was permanently disabled temporarily by brute force protection." contains an extra "temporarily" that should be removed.

Maybe someone from the core-iam team like @sguilhen can have a look.

Unreported flaky test detected

If the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR.

org.keycloak.testsuite.webauthn.registration.WebAuthnOtherSettingsTest#apiSecurityErrorMessage

Keycloak CI - WebAuthn IT

org.openqa.selenium.WebDriverException: 
unknown error: unhandled inspector error: {"code":-32000,"message":"Node with given id does not belong to the document"}
  (Session info: chrome=150.0.7871.128)
Build info: version: '4.28.1', revision: '73f5ad48a2'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '6.17.0-1020-azure', java.version: '25.0.3'
...

Report flaky test

IMO this is a worthy addition. We do have a mechanism to send emails based on certain events, but Workflows can enable other strategies well beyond that. For example, one could set a required action in response to such an event in addition to sending the email. Or notify the admins in addition to the user. The scenario depends on the requirements of each deployment, but in my mind it does make sense to support these events.

Rebased to re-run the failed flaky build. Might have been caused by #47482