fix: shortcuts conflict with browser native shortcuts

[majidzeno]

• Closes #20222

User facing changelog

Cypress shortcuts updated to not conflict with the browser native shortcuts

Additional details

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?
• Have new configuration options been added to the cypress.schema.json?

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[CLAassistant]

All committers have signed the CLA.

[majidzeno]

@jennifer-shehane CI is failing, seems there is an issue with desktop-gui, can you check 🙏 ? Is there anything from my side I can do?

[jennifer-shehane]

@majidzeno Is it possible to add a test around this behavior? The failures look like flaky tests.

[majidzeno]

@jennifer-shehane I tried to reproduce this issue locally but the test passed, I checked the test and the onMount function seems to fire as expected, can we try to rerun the CI from the failed task once again? 🙏

[majidzeno]

@jennifer-shehane I rebased my branch to the develop and seems the issue is still happening, this is weird cause it had to be already fixed before here, I will check this PR to find the why it is still flaky

[majidzeno]

@jennifer-shehane the flaky test is this.ipc.getUserEditor is not triggered every time, I think the reason behind that is the nature of useEffect which is used in onMount, it is triggered in first but the events will not flush until the next update, I think this solution is a bit hacky but I forced the component to update by changing the state, check the last commit.

[BlueWinds]

@majidzeno - I went ahead and pushed a test for these changes onto your branch, this is what @jennifer-shehane was asking for.

Looks good to me. 👍

[jennifer-shehane]

Kitchensink is failing in 'test-cypress-scaffold' due to known reasons that we're working on resolving.

[BlueWinds]

Given that we know the test failure is unrelated (and I'm working on it in a separate ticket), I'm going to merge this as-is. Thanks for your contribution, @majidzeno :)

[majidzeno]

@BlueWinds @jennifer-shehane Thanks a lot 🙏
That was my first contribution to cypress btw 😄