[planning] create testing strategy for web IDE to avoid regressions

This is a planning issue.

Why is this here

IDE is facing regular regressions, impacting customers and resulting in reverts. To tackle this it's necessary we invest in our testing strategy and work on the quality efforts to help us detect regressions early and prevent them from going out ideally.

What's expected

This issue can be closed successfully when

• Strategy and goals are described in this issue
• Have a plan to make sure the expected path to interact with the IDE is tested
• Strategy to test the most common workflows
• Follow Up Issues are created and assigned to &2578