[DAC-Question]: Decide on how DAC client binary handles different major API versions

The question raised as part of the !8678 (comment 1386693087).

To sum up, dac client binary is client binary for interacting with dac network. When we will have multiple versions of the DAC API, the client may want to specify which API to interact with. This may be solved with:

1. Independent client binary for every major API version, i.e. bin_dac_client_v0, bin_dac_client_v1 etc?
2. Alternatively we could have a command inside bin_dac_client that sets the configuration of the API that we want to use? Which would dispatch the requests using correct API.
3. We simply default (hardcode it) to the latest API version? (we do this now basically and is not a problem since we only have one :) ). Note that the problem of this approach is that the client can only use the latest version.

Additionally, should client binary regression test account for different API version then?