Address discrepancy in EKS-D version in OVA vs validations for CLI

Based on the version of the CLI, we require that certain tags be present on the OVA depending on the EKS-D release specified in that version of our bundles. However now that the responsibility falls on the user to build these OVAs for Ubuntu, it is not clear what versions to tag these OVAs in VCenter, nor will it match what is actually present in the OVA because it always contains the latest version. #3355 raises an issue with the lack of documentation in what these tags are and where to retrieve them, but they don't match the version stored in the OVA.

There are a couple of things we need to evaluate:
1. Add clearer documentation on where to retrieve these tags and how to tag based on the version of the CLI you have.
2. Remove the necessity of these tags. We had these are safe guards in the past to avoid using an older version of the OVA with newer version of the CLI, which can cause compatibility issues. If we can come up with a different way to validate the versions, that would remove the need to be able to tag, but we had issues in the past in being able to do that.
3. Add another CLI command that auto tags self-built OVAs for the user. We can retrieve the tags we need from the bundle anyways, and call the necessary commands to tag for the user.

I think option 2 is the best approach, but not sure how feasible it is. Option 1 is cumbersome for the user, so option 3 would be the next best option.

The issue names no files, tests, or entry points. Start by tracing the CLI's EKS-D bundle validation and the OVA tag requirements, then determine which of the three proposed approaches is feasible; done means a defined compatibility check or documented and automated tagging workflow.

Written by the indexing model from the issue text.