feat: enable application performance profiling (#8442)

# Which Problems Are Solved

To have more insight on the performance, CPU and memory usage of
ZITADEL, we want to enable profiling.

# How the Problems Are Solved

- Allow profiling by configuration.
- Provide Google Cloud Profiler as first implementation

# Additional Changes

None.

# Additional Context

There were possible memory leaks reported:
https://discord.com/channels/927474939156643850/1273210227918897152

Co-authored-by: Silvan <silvan.reusser@gmail.com>

cmd/defaults.yaml

@@ -25,6 +25,18 @@ Tracing:
   # The endpoint of the otel collector endpoint
   Endpoint: "" #ZITADEL_TRACING_ENDPOINT
 
+# Profiler enables capturing profiling data (CPU, Memory, ...) for performance analysis
+Profiler:
+  # Choose one of "google" and "none"
+  # Depending on the type there are different configuration options
+  # for type 'google'
+  # ProjectID: google-project-id
+  #
+  # type 'none' or '' disables profiling
+  Type: none # ZITADEL_PROFILER_TYPE
+  # projectID for google
+  ProjectID: ''  # ZITADEL_PROFILER_PROJECTID
+
 Telemetry:
   # As long as Enabled is true, ZITADEL tries to send usage data to the configured Telemetry.Endpoints.
   # Data is projected by ZITADEL even if Enabled is false.