Programmatic way to determine whether new EKSA release requires a new OS/VM image

**What would you like to be added**:
As an eks-a administrator, I would like to have a reliable and programmatic way to determine whether a new EKSA release requires a new OS/VM image.

Acceptance Criteria:
1. Should allow automating the process of building a new image for a new EKSA release whenever it's necessary
2. Should be able to validate that a given OS image has all the required binaries cached (e.g. ETCD'd binary fo a target release version)

**Why is this needed**:
If our users are building their own images, they want to be able to validate these images are acceptable for a given EKSA release

The issue names no files, tests, or entry points. Begin by locating the EKSA release and OS/VM image-building workflows, then determine how a release declares required binaries and how an image can be validated against them. Done means both acceptance criteria are automatable and documented for administrators building their own images.

Written by the indexing model from the issue text.