Fix backward compatibility

[RogerZhongAWS]

Motivation

• Localproxy v3.1.1 does not work with localproxy v3.1.0 and localproxy v2 in certain scenarios.

Modifications

Change summary

• Removed check on single service Id to fall back to V1 mode and instead trigger V1 mode based on user input only.
• Added command line options for passing either V1 or V2 as a destination-client-type to switch between different backward compatible modes

Revision diff summary

If there is more than one revision, please explain what has been changed since the last revision.

Testing

Is your change tested? If not, please justify the reason.
Please list your testing steps and test results. v3.1.1 localproxy → v3.1.1 localproxy

v3.1.1 localproxy → v3.1.0 localproxy

v3.1.0 localproxy → v3.1.1 localproxy

v3.1.1 localproxy → v2.3.1 localproxy

v2.3.1 localproxy → v3.1.1 localproxy

v3.1.1 localproxy → DC v1.9 using latest SDK

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.