Mark Framework Version in Resources to Support Framework Related Updates

Original idea comes from @shawkins .

The framework might add an annotation to resource(s) - primary might be sufficient - to support updates of the framework. For example from v4.3 -> v4.4 we started to use SSA on Dependent Resources by default (added feature flag to use previous approach), where in some cases the update might not be trivial. Such an annotation would widen our possibilities, and we could make runtime decisions based on that. For example If a resource was before created/managed by older version of framework, we could decide to use the legacy approach automatically.

Note also that the annotation needs to be added by the framework, we already add finalizer (if needed) in a phase before the first reconciliation, this could be added in the same step if needed.

No se nombran archivos ni pruebas. Empieza siguiendo el paso de pre-reconciliation del framework en el que se añaden los finalizers y, a continuación, determina cómo deben registrarse y consumirse los metadatos de la versión del recurso durante las actualizaciones; se considera terminado cuando el framework puede distinguir los recursos creados o gestionados por versiones anteriores y aplicar el comportamiento de compatibilidad previsto.