Migrate to a Single Tinkerbell Version

[chrisdoherty4]

Tinkerbell is composed of several microservices. All Tinkerbell microservices are semver major version 0 and we have historically made breaking changes in minor version increments. The volatile nature of major version 0 has made it difficult for users to know which versions of our services are compatible with eachother.

This ticket is to track migration to a singular version that represents a set of known to work versions of the Tinkerbell microservices.

[chrisdoherty4]

A lot of work has gone into the Helm charts and the playground repositories that pushes us towards a single deployable version. The stack chart essentially represents the singular version of working Tinkerbell services.

We haven't updated the docs site to reflect these changes (and many other changes) and we haven't formally talked about what needs doing to declare this version the first point of engagement for users, though I suspect this issue can be wrapped up soon after some discussion.