Extended Cache Management

[mcopik]

SeBS keeps a local cache of all deployed cloud resources and locally created artifacts, e.g., function builds. To support distributed deployments, we should support a mode where we merge the cache from N existing caches - remove duplicates without losing allocated resources, as long as they share the same SeBS resource ID. This should also drop local resources, as such merged cache should be usable on any machine.

[sanskar-singh-2403]

Hi @mcopik, I'd like to take this one up.

To make sure I'm aligned before diving in, here's my understanding of the goal:

• Add a mode that merges N existing SeBS caches into a single cache.
• Deduplicate entries by SeBS resource ID, keeping allocated cloud resources so nothing gets orphaned.
• Drop local-only artifacts (e.g. function builds and other machine-specific state) so the merged cache is portable across machines.

A couple of questions to confirm scope:

1. Should this be exposed as a new CLI command (something like sebs.py cache merge <cache_a> <cache_b> ... -o <out>), or an option on the existing cache handling?
2. On conflict for the same resource ID with differing values, what's the preferred resolution: last-writer-wins, first-writer-wins, or fail loudly and require manual resolution?
3. For "local resources" to drop, is the intended rule "anything under the code_package / build artifact paths" or is there a specific set of keys you want stripped?

I've cloned the repo and started reading through sebs/cache.py. Happy to open a draft PR once the direction above is confirmed. Could you assign this to me?