Add experimental.input.forceVT setting to the interaction page

[cinnamon-msft]

Closes #137

[opbld31]

Docs Build status updates of commit c36e47f:

✅ Validation status: passed

File	Status	Preview URL	Details
TerminalDocs/customize-settings/interaction.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[mattwojo]

Force the terminal to use the legacy input encoding. Specific keys in some applications may stop working when enabling this setting, but it can be useful for advanced-level scenarios when debugging input issues, especially with the debug tap.

[DHowett]

If we're gonna link to docs on the debug tap... people will be surprised/appalled that they are not localized

[opbld30]

Docs Build status updates of commit 985edc2:

✅ Validation status: passed

File	Status	Preview URL	Details
TerminalDocs/customize-settings/interaction.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[mattwojo]

Ugh... interesting point @DHowett. Do you anticipate there being a broad interest in debug tap? Or is this based on linking to anything from the docs that isn't localized?
If there's a broad interest, maybe we should move this onto docs.microsoft. If it's just based on linking to anything not localized, we did update to point out that this is for advanced level specific scenarios and I'd imagine that in those cases the customer would also need to know other areas of content on the product repo as well (true or am I imagining that?)

[DHowett]

Ugh... interesting point @DHowett. Do you anticipate there being a broad interest in debug tap? Or is this based on linking to anything from the docs that isn't localized?
If there's a broad interest, maybe we should move this onto docs.microsoft. If it's just based on linking to anything not localized, we did update to point out that this is for advanced level specific scenarios and I'd imagine that in those cases the customer would also need to know other areas of content on the product repo as well (true or am I imagining that?)

That's a fair enough take. I don't anticipate there being broad interest in it it -- we bust it out when there are issues we think the user can help us get to the bottom of, but it's very much not our first port of call.

[mattwojo]

I vote that we ship it and then assess whether we get enough feedback about translating that debug tap tool to consider moving it to docs.ms so that it can be translated and utilized more broadly.