Introduce a `versions` subcommand

**What would you like to be added**:

EKS-A is a conglomerate of other tools. It would be useful from both a users and maintainers perspective to be able to easily identify what versions of the various tools contribute to an EKS-A release.

For example:

```
$ eksctl anywhere versions
EKS Anywhere v0.20.0
Cluster API v1.4
Etcdadm Bootstrap Provider v0.5
Cluster API Provider Tinkerbell v0.3
Cluster API Provider Tinkerbell v0.3
Tinkerbell v1.3
Flux v0.4
...
```

**Why is this needed**:

Providing this data will help users perform debugging and maintainers understand exactly what went into a release without the need to evaluate source code and build system history/logs.

The issue names no files, tests, or entry points. Start by locating the eksctl anywhere CLI command definitions and the release metadata that records component versions. The work is done when an `eksctl anywhere versions` command reports the EKS Anywhere release and its contributing tool versions in a format matching the example.

Written by the indexing model from the issue text.