TA-3971: Add option to export packages by versions

[Buqeta]

Description

• Added an option to the existing config export command --keysByVersion which exports the packages by the specific received versions.
• Added logic to check if both versions are being sent or neither of them isn't sent, so the command fails with a message.
• Used the same batch export logic, just added a check that controls which batch export endpoint will be called based on the received option.
• Added test cases that are the same as batch export cases.
• Updated CLI version.

Checklist

• I have self-reviewed this PR
• I have tested the change and proved that it works in different scenarios
• I have updated docs if needed

[ksalihu]

I think the command should be config versions export {resource} {action}

[Buqeta]

I think the command should be config versions export {resource} {action}

We're technically exporting packages. The version is just a property of the package. I don't think it's a resource on its own. This structure you're proposing is also confusing to the CLI user since the config export exports packages and it doesn't have the packages name in the command.

[ZgjimHaziri]

We're technically exporting packages. The version is just a property of the package. I don't think it's a resource on its own. This structure you're proposing is also confusing to the CLI user since the config export exports packages and it doesn't have the packages name in the command.

The main point here is that the existing export command is not in a proper structure.