consider shared resources (across deployments in the state file) for assets

[blake-mealey]

To avoid duplicate uploads (especially to reduce costs for audio uploads) for the same assets across experiences, asset resources could be saved in a parallel shared graph in the state file. Then the aliases would be dependent on that graph and the experience in the per-deployment graphs, and would be saved per deployment.

[blake-mealey]

Tentatively adding this to milestone v1.0.0. On the fence about it, but I like the idea of prioritizing performance and scaling issues before v1.0.0. However, I don't think this is likely to cause breaking changes (it would cause breaking changes to the state file API but that should be handled gracefully under the hood with a migration) so I'd be OK with releasing later.

[jcphlux]

I know what was suggested to me to help with the clutter of assets from multiple experiences in my group was to put all assets for an experience in a separate group. Being able to deploy the experience to one group but put all the assets in a different group would be useful.