Fix up Remote Access API names (#17923)
Closes #17821
Closes #17866
Summary of the issue:
Remote's API uses snake_case in some parts, where internal style is to use camelCase.
Description of user facing changes
None.
Description of development approach
Mark the remoteClient as internal
Rename source/remoteClient to source/_remoteClient in VS Code, and allow it's refactoring tools handle most replacements
Manually fix errors with unit tests (all due to unittest.mock requiring package names in quotes.
Rename Remote's config items to use camelCase
Inspect the config spec for items in the [remote] section that use snake_case.
For each of them, perform a global find and replace, verifying each match was a candidate for replacement (for instance, connection_type can only be renamed where it pertains to the config, not where it is part of the protocol)
Update the config migration
Bump the config schema version
Add a profile upgrade step that renames any remote config to have its new name
Add unit tests for same
