Enable/Disable Templates

### The required feature described as a wish

After working more extensively with ACS, I’ve noticed several missing features that are necessary for effective template management.

When uploading a modified version of an existing template (for example, Rocky9), we are forced to give it a new name rather than following our established naming scheme, in order to avoid confusion with the old version. We also cannot simply delete the old template, as it is already in use by multiple production instances.

As a result, an Enable/Disable feature is needed. This would allow older templates to be disabled while keeping updated or approved templates active. Existing instances would continue running on the old templates, while new instances would be created using the enabled, updated ones.

No se nombran archivos, pruebas ni puntos de entrada; comienza rastreando los flujos de carga de plantillas de ACS y de creación de instancias. Define y verifica el comportamiento de habilitación/deshabilitación para que las instancias existentes conserven sus plantillas y las nuevas instancias seleccionen solo las plantillas habilitadas.

Escrito por el modelo de indexación a partir del texto del issue.