Backport fix: Detect CORS problems in Web IDE

What does this MR do and why?

This Merge Request backport the fix delivered on Merge Request !200350 (merged) targeting the 18.2 stable release.

NOTE This fix requires updating the Web IDE npm package because part of the changes required to fix the bug are in this artifact (see gitlab-web-ide!553 (merged)). A side-effect of updating the NPM package in this backport fix is that it also updates the GitLab Workflow Extension to version 6.35.1 (see gitlab-web-ide!551 (merged)). I recorded a video where I verify that this update doesn't introduce regressions caused by version incompatibility in Duo Chat and Duo Code Suggestions. This version update also doesn't introduce new features to the Web IDE.

backport_fix_18_2.mov

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch.
• The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes).
• The MR title is descriptive (e.g. "Backport of 'title of default branch MR'"). This is important, since the title will be copied to the patch blog post.
• Required labels have been applied to this merge request
  • severity label and bug subtype labels (if applicable)
  • If this MR fixes a bug that affects customers, the customer label has been applied.
• Set the milestone of the merge request to match the target backport branch version.
• This MR has been approved by a maintainer (only one approval is required).
• Ensure the e2e:test-on-omnibus-ee job has either succeeded or been approved by a Software Engineer in Test.

Note to the merge request author and maintainer

If you have questions about the patch release process, please:

• Refer to the patch release runbook for engineers and maintainers for guidance.
• Ask questions on the #releases Slack channel (internal only).
• Once the backport has been merged, the commit changes will be automatically deployed to a release environment that can be used for manual validation. See after merging runbook for details.