Add `config-pull` command to the CLI

[chelma]

Description

As a part of https://github.com/arkime/aws-aio/issues/87, this task is to add a way to pull the code/config bundles that have been deployed to the Capture and Viewer nodes from the cloud to their local machine.

Acceptance Criteria

• Users have a way to retrieve a specified config bundle to their local machine

[chelma]

I think we can piggy-back on some of the UI assumptions from config-list (see https://github.com/arkime/aws-aio/issues/139), and have a pretty reasonable experience:

• Add a config-pull command
• User specifies to retrieve either the --capture or --viewer config, along with a --config-version. The --config-version corresponds to the config_version in our bundle's metadata, which we will need to make clear.
• Flags to pull the --current and --previous would be easy and useful as well.
• The CLI will pull the object from S3 and stick it in a default location in the user's workspace based on the cluster name/config type/config version/etc. Something like: .../aws-aio/Config-MyCluster-AccountNum-AwsRegion-Capture-v6.zip. Having unambiguous bundles names will hopefully prevent operational mistakes.
• I'm leaning away from sticking the downloaded bundle directly into the user's config directories by default for a few reasons: we would need to ensure the directory exists, the contents of the directory are effectively source code and likely under revision control, and it feels a bit more "surprising" to have them appear there (personally).

[chelma]

Code merged; acceptance criteria met. Resolving.