Namespace mappings and ad-hoc connection selection

[Phil W]

Allow namespace mappings to be defined as part of the connection, regardless as to whether it is selected for the module, so that a deployment that uses an ad-hoc connection correctly applies the required mapping from that ad-hoc connection rather than the module's configured connection.

I'm asking for this as the recommended workaround of using a special deployment branch isn't one we wish to adopt (we additionally do not [yet] store any IDE files in git), and the faff of updating the module's selected connection will be somewhat irritating compared with the simple exercise of making an ad-hoc connection selection in the deployment scope dialog.

[Scott Wells]

Issue tracker grooming. If this is still an issue, please feel free to reopen, ideally with a concrete reproduction scenario.