Add support for more DSR queries.

[j4james]

Summary of the Pull Request

This PR adds support for more Device Status Report (DSR) queries,
specifically:

• Printer Status (DSR ?15)
• User Defined Keys (DSR ?25)
• Keyboard Status (DSR ?26)
• Locator Status (DSR ?55)
• Locator Identity (DSR ?56)
• Data Integrity (DSR ?75)
• Multiple Session Status (DSR ?85)

Detailed Description of the Pull Request / Additional comments

For most of these, we just need to return a DSR sequence indicating
that the functionality isn't supported.

• DSR ?13 indicates that a printer isn't connected.
• DSR ?23 indicates the UDK extension isn't supported.
• DSR ?53 indicates that a locator device isn't connected
• DSR ?57;0 indicates the locator type is unknown or not connected.
• DSR ?83 indicates that multiple sessions aren't supported.

For the keyboard, we report DSR ?27;0;0;5, indicating a PC keyboard
(the 5 parameter), a "ready" status (the second 0 parameter), and an
unknown language (the first 0 parameter). In the long term, there may
be some value in identifying the actual keyboard language, but for now
this should be good enough.

The data integrity report was originally used to detect communication
errors between the terminal and host, but that's not really applicable
for modern terminals, so we always just report DSR ?70, indicating
that there are no errors.

Validation Steps Performed

I've added some more adapter tests and output engine tests covering the
new reports.

PR Checklist

• Closes Add support for more DSR queries #16518
• Tests added/passed

[j4james]

I should note that I've also tried to verify these reports in Vttest, but there were some bugs in their DSR handler which have only just been fixed in the latest release, and even now the DSR ?23 report for UDK isn't identified correctly (this is probably my fault - I must have missed that one when I was reporting the other bugs). I didn't want to put this in the PR commit notes since it's likely just a short term issue.