Similar to logging, we'd want data-service to stay free of direct dependencies on compass sevices that are dependency injected in other parts of the application otherwise. Right now it seems like data-service is using preferences directly to pull information about user proxy configuration before applying those options during connection creation.

We'd like to remove this direct coupling by either changing data service to accept preferences through dependency injection similar to logging service, or by some other means, for example by passing these as part of "adjusted" connectionInfo in the connection flow in compass-connections (we already do some connection info modification there before it reaches data-service / devtools-connect, so might as well map preferences to data-service connection info there)