F16 Is not usable in Terminal

### Windows Terminal version

1.16.10261.0

### Windows build number

10.0.19044.2604

### Other Software

Happens running cmd or pwsh 7.3.2 within the tab.

### Steps to reproduce

Have a keyboard with additional function keys.
Run an app that reports key presses.
In terminal F13, F14, & F15 work. But F16 does not: no input is seen. Also cannot map to a WT action.

The test application works with F16 (including with modifiers) under conhost.exe. Also seen (and mappable) in Visual Studio 2022 (didn't check earlier versions).

### Expected Behavior

See keyboard input when F16 is pressed. Can map to actions, and when pressed that action is triggered.

### Actual Behavior

F16 does nothing in Windows Terminal and applications running within Windows Terminal.

Start by reproducing the missing F16 input in Windows Terminal using an application that reports key presses, and compare it with conhost.exe or Visual Studio 2022 behavior. Done means F16, including modifiers, is delivered to applications and can be mapped to a Windows Terminal action.

Written by the indexing model from the issue text.