nvda

aa6bb8fa - Migrate remaining internal consumers off the deprecated brailleInput module (#20595)

Migrate remaining internal consumers off the deprecated brailleInput module (#20595) Follow-up of #20509. Together with #20594 this completes the internal migration off the deprecated brailleInput module. Summary of the issue: #20509 moved braille input handling into the braille.input package. The old brailleInput module became a backwards compatibility shim that logs a deprecation warning on attribute access. #20594 migrates the call sites that hit the shim on every event. The remaining internal consumers touch the shim once per session. Most braille display drivers reference brailleInput.BrailleInputGesture in a class definition, evaluated once at driver import. core calls brailleInput.initialize and terminate at start, shutdown and configuration reset. The braille settings panel accesses brailleInput.handler.table when opened or saved. These accesses still log deprecation warnings and keep internal code on a deprecated path. Description of user facing changes: None. Description of developer facing changes: None. The deprecated brailleInput shim is unchanged and keeps serving add-ons. Unit tests now cover the shim surface. Description of development approach: Migrated the remaining internal consumers to the new import locations. Braille display drivers now use braille.input.gesture.BrailleInputGesture directly. core, gui.settingsDialogs, _remoteClient.input and the unit test bootstrap import braille.input. Added regression tests to tests/unit/test_braille/test_publicSurface.py. They assert that resident names on braille.input do not warn. They also assert that every deprecated brailleInput name warns and resolves to the correct object.