[Terminal]: JAWS Screen Reader Cursor mode does not work inside Terminal app.

### Windows Terminal version

1.12.3472.0

### Windows build number

10.0.22504.1010

### Other Software

**Test Environment:**
OS: Windows 11 Version Dev (OS Build 22504.1010)
App: Windows Terminal Preview
Screen Reader: JAWS 2021

### Steps to reproduce

**Repro Steps:**
1. Open Windows Terminal.
2. Open Settings page using 'Ctr+,'.
3. Activate 'Actions' tab and then Add a new actions 'Set tab color' with shortcut key 'Ctrl + Shift + c'.
4. Open JAWS 2021 Screen Reader.
5. Navigate inside Terminal window.
6. Turn on Cursor mode using 'Insert + Z' and then try to read static/non-interactive/non-tab able content.
7. Observe the issues.

**User Experience:**
JAWS Screen Reader users are impacted here as JAWS users are not able to read static/non-interactive/non-tab able content.

**Attachments:**
[JAWS Screen Reader Cursor mode does not work inside Terminal app..zip](https://github.com/microsoft/terminal/files/7782791/JAWS.Screen.Reader.Cursor.mode.does.not.work.inside.Terminal.app.zip)

### Expected Behavior

JAWS Cursor mode should work inside Terminal app.

### Actual Behavior

JAWS Screen Reader Cursor mode does not work inside Terminal app as result JAWS users are not able to read static/non-interactive/non-tab able content.

**Observation:**
Issue does not repro with Narrator & NVDA as Scan mode work fine inside Terminal app.

Start with the Windows Terminal accessibility behavior described in the reproduction steps and inspect the attached JAWS report. Compare JAWS Cursor mode with the stated Narrator and NVDA Scan mode behavior while following the Settings and custom action setup. Done means JAWS can read static, non-interactive, non-tabable content inside Terminal.

Written by the indexing model from the issue text.