fix: navigation key names

[AlexDubok]

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change? (check one)

• Yes (but a small one) :)
• [] No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• It's submitted to the dev branch.
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• All tests are passing: https://github.com/vuejs/vue-test-utils/blob/dev/.github/CONTRIBUTING.md#development-setup
• New/updated tests are included

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
When using keyboard events (keyup, keydown), the key event param is passed incorrectly for navigation keys. it should be ArrowRight instead of just Right according to the same document that is referred in the code: https://github.com/ashubham/w3c-keys/blob/48d9dc98a6468447bc15db8d4b15ce19ce157869/index.ts#L17

Left, Right, Up and Down were used in Internet Explorer, Edge (16 and earlier), and Firefox (36 and earlier) according to MDN. Those browsers are so old that they are deprecated.

[netlify]

❌ Deploy Preview for vue-test-utils-v1 failed.

Name	Link
🔨 Latest commit	4ee42fd
🔍 Latest deploy log	https://app.netlify.com/sites/vue-test-utils-v1/deploys/63bc8a619fd85b00084f47a7

[lmiller1990]

Any chance you can add a test for this? Thanks!

[AlexDubok]

Any chance you can add a test for this? Thanks!

Sorry, but there is test already. I just updated expected values according to the common spec.