Document an understanding of the SW replication and repository requirements for SRCs and suggest potential implementations

We have some exposure to different software distribution implementations within the SRCNet ART and its teams. Before we launch a prototype service we should take stock of the interplay between (previously defined, but possibly incomplete) requirements and the emerging SRCNet architecture to see how to proceed, and to understand and document the use cases supported by examples such as EESSI (and cvmfs) vs container registry system vs other examples (e.g. git) that might be more suitable for use-generated sw.