New containers ci

[garciagenrique]

New container CI logic

• Removes eos-fuse-mount container --> #TODO the way things were done should be saved somewhere in the documentation (deprecated section?)

• Missing a Readme to explain everything.

• Every time the base-ops container/content is changed, a small version must be released (i.e., v.X.Y.(Z+1)).

  • This will trigger a 2 steps workflow:
    1. Building of the vre-base-ops:vX.Y.Z+1 image
    2. Building of all the rest of images that depends on the changes done to the base-ops layer.

• In any other situation, a workflow will be triggered only if any change is detected on any of the containers folders/files. The container will be based on the latest vre-base-ops tag. Ref. add CI that builds containers when changes in subdir #260

Closes #236