node:readline support reading non printable characters such as group separator

What is the problem this feature will solve?

When using a USB barcode reader on a TTY app that uses node:readline the group separator character \x1d is needed for GS1-128 barcodes. GS1-128 barcodes contain multiple elements defined by an Application Identifier (AI) that is a 2-4 digit code followed by value. Either a defined length is expected for the data or it looks for the group separator character for early termination of the value.

What is the feature you are proposing to solve the problem?

accept some or all non printable characters as inputs to readline

One of the following

1. add a flag to turn on that by default is disable to preserve existing implementations
2. add an option to explicitly define allowable non printable characters, defaults to an empty list
3. both a global flag and a list

What alternatives have you considered?

I've considered writing my own, seems like a bad idea for support and security. I may look into putting in a PR but I'm starting with a feature request.
I've considered rewriting the application into a non NodeJS application.
I've considered just replacing the TTY app with something more "modern" but there are external layers affecting this decision. This wouldn't allow copy/pasta of other characters which could be useful in some edge cases.

Start by examining node:readline's TTY input handling and how it currently treats non-printable characters. The issue proposes either a global flag, an allowlist, or both, so a contributor would first need to resolve that design choice. Done means the group separator can be read without breaking existing readline behavior, with coverage for the chosen option.