[oss] Rebrand the project

[eskultety]

Cachi2 has inherently always had this 'caching' connotation coming from its predecessor - cachito. The truth is, however, that we've never done or provided means of any long term caching of fetched dependencies (unless consumers of cachi2 backed up the directory on the file system we create themselves). We should either try coming up with a name that better describes the ultimate mission of the project - securely prefetch build dependencies for a network isolated (i.e. hermetic) build, recording them in an accurate SBOM - or fall back to some catchy, random non-descriptive name not confusing anyone at all.

[pierDipi]

SealFetch or SealDeps ?

[ben-alkov]

Seems like a good first step might be brainstorming keywords which describe what the project's mission/purpose is (i.e. "fetch" and "secure" immediately come to mind for me, and indeed @eskultety used those terms above).

[eskultety]

@pierDipi FYI #711 :)