Fix up API symbols introduced in 2025.3 patch releases (#19630)
### Link to issue number:
Follow-up nvaccess/nvda@a8f4f802c3
Follow-up nvaccess/nvda@1a9a5e8003
### Summary of the issue:
The patches introduced in 2025.3.1 and 2025.3.3 introduced new Windows
API bindings. As the project's approach to these bindings has changed a
lot in the transition to 64-bit, and as patch releases avoid introducing
changes to the API (including additions), these prototypes were marked
internal.
### Description of user facing changes:
None.
### Description of developer facing changes:
The following symbols are now part of the public API:
`systemUtils.getCurrentProcessToken`;
`utils.security.isRunningElevated`;
`winBindings.advapi32.TokenAccessRight`, `TOKEN_INFORMATION_CLASS`, and
`TOKEN_ELEVATION_TYPE`; and `winBindings.kernel32.WAIT`, `PAGE`,
`CreateFileMapping`, `FILE_MAP`, `MapViewOfFile`, `UnmapViewOfFile`, and
`OpenFileMapping`.
### Description of development approach:
Used VS Code's refactoring tools to move the above listed function,
enumerations and ctypes prototypes from `_remoteClient.secureDesktop`
and `utils.security`, removing their underscore prefixes in the process.
Added the `desiredAccess` parameter to
`systemUtils.getCurrentProcessToken` (previously
`utils.security._getCurrentProcessToken`) and pass that to
`OpenProcessToken`, rather than the previously hardcoded `TOKEN_QUERY`
value.
### Testing strategy:
Unit and system tests.
### Known issues with pull request:
None known
