Fix flaky code-editor-actions actions test

[tplevko]

Found the source of instabilities for code-editor-actions tests in Chrome and Edge. The backend updates the yaml in editor on save - changing the indentation. This change is sometimes detected, sometimes not by the monaco editor, but only on these two browsers - didn't see this error in FF. I also didn't find too much about the "undo" function. The alert is therefor a bit unpredictable, however the test was adjusted to verify the alert after the second "undo" invocation, where the alert fires regularly.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
1.5% Duplication

[lordrip]

Thanks for investigating this @tplevko 💪

[lordrip]

I also didn't find too much about the "undo" function. The alert is therefor a bit unpredictable, however the test was adjusted to verify the alert after the second "undo" invocation, where the alert fires regularly.

Expanding a bit on what you're mentioning @tplevko, does this mean that the very first undo click doesn't work? If that's the case maybe there's a bug on the UI side then 🤔

[tplevko]

@lordrip actually yes - this is however related to the way the editor handles the imported integration from file - e.g. the EipAction.yaml get's imported - is a valid yaml, but it actually contains indentination and some characters (e.g. double quotes instead of single quotes), which are actually replaced in the UI after the roundtrip to the backend, where the integration is parsed and the result is sent to the UI.

In this case - the first "undo" click really does nothing besides reverting the integration to the one which was imported.