Standardize view deployment for archived binaries

[psakievich]

One of the intents of spack-manager is to allow for archives of binaries on a local machine. The goal of these archives are to

1. Be accessible for modules
2. Easily defined as externals in spack environments to limit rebuilds required

These should support the developer and analyst workflows and be independent of spack in case things need to be deleted or updated. The current plan is to use copy views to create these caches. The other ideas is that they should be stored in the local $SPACK_MANAGER/views directory.

However, we need a standardized naming convention/archival procedure. Some of the fields that need to be captured are

• compiler/mpi combo
• build date
• software project (exawind/pele/etc)
• product name (?)

These are a lot of fields and potential logic, and there are binary path relocation issues to consider. So perhaps a hash might be acceptable for handeling some of this data, but that will also need an API so devs can easily access the archives they wan.