Add new shortcuts for Visual Studio

Description

Related Issue

Motivation and Context

Visual Studio was lacking commands for a few basic features, specifically Go Back, Go Forward, Go to Definition, and Show References which I shortened to Show Refs.

resume was an odd name for a command that begins a debug session, although it is the same keypress as a continue action when debug hits a breakpoint, so I also added an additional phrase go to debug to the f5 keypress.

How Has This Been Tested

These changes were tested in use against Visual Studio Professional 2019 and are voice commands for existing keyboard shortcuts. I believe these are all keyboard shortcuts that I used on previous versions of Visual Studio but no longer have them installed to verify.

I see in the checklist a reference to writing actual tests against the code, but I didn't see the tests and the Contributing document does not reference how to create such tests, and I didn't see any documentation for tests in the code, so I did not run or contribute to any automated testing.

Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue or bug)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Renamed existing command phrases (we discourage this without a strong rationale).

Checklist

[x] I have read the CONTRIBUTING document.
[x] My code follows the code style of this project.
[x] I have checked that my code does not duplicate functionality elsewhere in Caster.
[x] My code implements all the features I wish to merge in this pull request.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests pass.

Maintainer/Reviewer Checklist

[x] Basic functionality has been tested and works as claimed.
[x] New documentation is clear and complete.
[x] Code is clear and readable.

Thank you for the PR and everything looks great!

I see in the checklist a reference to writing actual tests against the code, but I didn't see the tests and the Contributing document does not reference how to create such tests, and I didn't see any documentation for tests in the code, so I did not run or contribute to any automated testing.

For the time being automated testing is mostly used in core code of Caster. Testing grammars is needed for applications but some further infrastructure is needed OS accessibility APIs. Leveraging accessibility APIs to grab cursor index, text, selected text, relative to the cursor position and menu items we could standardized tests for applications and associated grammars. Not only would that be possible but re-implementing Dragon Select-and-Say capability and specific functionality for navigating code by voice.

dictation-toolbox / Caster