3 Tier Architecture - Cloud, Multiple On-Prem, with Edge Devices

### Description

Problem: Many customers are choosing on-premise deployments of FlowFuse at site locations rather than corporate-level deployments. If customers continue expanding via this model, they will deploy more site-level solutions. Eventually, they will want to orchestrate their deployments.

The ideal deployment method is to deploy at the site level. It is important to Leverage Instance features rather than device features. Important features include the granularity of the settings differences. Customers may also leverage remote devices for edge deployments, but the platform will be deployed on-premise.

Example Deployment Architecture (Rutimes at the Corporate Level are less important):


Desired Features from Corporate Orchestration:

- Team Library Syncing
- Proxy Access to the site platform
- Audit Log Aggregation
- Software Bill of Materials
- NPM Library Synchronization
- Health Status

Think of it as an Administration Solution for FF Platforms. Less of an unnecessary third layer.

References plus customers that would need something like this:
https://github.com/FlowFuse/flowfuse/issues/2542
https://app-eu1.hubspot.com/contacts/26586079/record/0-1/25738651
@zackwasli @MichaelBDavis Please share other customers that have asked for this. I will continue adding.

### Which customers would this be available to

Enterprise Tier Only (EE)

### Have you provided an initial effort estimate for this issue?

I can not provide an initial effort estimate