feat: able to specify custom key for input record

[mikedidomizio]

Pull Request Template

Description

Added the ability to change the keyboard command for recording input changes. By default this is TAB. There are a few closed issues that had discussion about how to remedy the tabbing and losing focus, but no solution.

This change allows users to change what key to finish input record to what they want. For instance I found SHIFT to be a better key.

This adds a button in the options menu, where a user clicks it and the extension listens for the next key down event.
I'm not a big fan of displaying the key code instead of the actual key but I didn't want to store both as one is only for display purposes.

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update
  This is up for debate, the documentation does mention the TAB key

How Has This Been Tested?

Ran the entire test suite that's provided and added unit tests to cover the new changes.

Checklist:

• My code follows the style guidelines of this project. npm run lint passes with no errors.
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes. npm run test passes with no errors.

[tnolet]

@mikedidomizio thanks for supplying this PR. We will review ASAP!

[maxigimenez]

LGTM 👍 , thanks for contributing @mikedidomizio!