[TriggersActionsUi] Regularly Failing Jest Config

[mistic]

The x-pack/plugins/triggers_actions_ui/jest.config.js jest config has shown to be problematic recently.

The error is being thrown during the run of this test suite on CI and logs as following (example):

var evt = document.createEvent('Event');
                   ^
TypeError: Cannot read properties of null (reading 'createEvent')

I'm not sure about what could be causing this but I think the warnings and console.errors that are being logged when running this suite could be a good place to start the investigation. For now, I'm just skipping the suite so you can have a look on those. Because of this non of the "unit" tests in the TriggersActionsUi plugin are being executed automatically. This can definitely lead to issues in future versions of Kibana if these tests are not fixed ASAP.

To unskip this test just remove the "x-pack/plugins/triggers_actions_ui/jest.config.js" item in .buildkite/disabled_jest_configs.json

Related to #144445

[elasticmachine]

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

[mikecote]

@XavierM I recall R&AM doing some work around the jest tests, is this issue covered already?

[jcger]

FYI Dec 14th we activated most of the test here and yesterday Jan 10th we activated everything except for two tests here.

We still want to fix those last two tests before closing this issue

[XavierM]

with this PR merged we can close this issue