Support Testnet/Devnet/Mainnet Deployment

#### Proposed Changes:

1. Separate the operator for network and simulation to support the independent startup of the network. This is because the simulation operator is intended for local testing and not needed for scenarios where ceramic network is deployed independently.

2. Supports dependency configuration for different network types (local/testnet/mainnet):
1. Replace ceramic's sqlitedb with postgresdb, and support configurable DB username/ name/password.
2. Support the ability to turn off ganache and cas.
3. Support configurable namespace for the network.

3. Add k8s ingress for ceramic to support public access for mainstream public clouds (AWS/GCP) since we need to expose Ceramic & ComposeDB APIs

4. Migrate Jaeger, Prometheus, and OpenTelemetry from the simulation operator to the network operator to create a universal monitoring and observability solution.
1. Expose js-ceramic's metric data to Prometheus.
2. Provision isolated metric and tracing data for each independent network service for each

5. Support log stream for ceramic and IPFS nodes.

#### Clarifying Questions:
1. Does these changes make sense?
2. Should These be merge into the current project or forked into a different repo?

The issue describes architectural changes to a Kubernetes operator for Ceramic networks. Start by examining the existing operator code to understand the current simulation setup. Look for network configuration, database dependencies (SQLite), and monitoring components (Jaeger, Prometheus). The goal is to separate network and simulation operators, add support for different deployment environments (local/testnet/mainnet), and integrate monitoring and logging. Check the repository for existing Kubernetes manifests and configuration files to understand the current structure.

Scritto dal modello di indicizzazione a partire dal testo della issue.