Allow overriding talos schematic and version through node annotations

[rkage]

Propose adding support for annotations specified on a node that supersede/override the TalosUpgrade CR.

At times it's necessary to use a different schematic and versions on Talos nodes in an environment. Handling these situations requires human involvement with access to talosctl

As an example, adding

tuppr.home-operations.com/schematic: 314b18a3f89d844efb2df46e362ff669ce4e49a7d74835cd365c54846acb822e
tuppr.home-operations.com/version: v1.10.7

to a node the tuppr operator evaluates the fields against what is current state and triggers upgrade reconciliation if there are inconsistencies. Post-upgrade/reconciliation the human administrator can determine if the annotations are safe to remove.