feat: add dry-run mode

[csatib02]

Introduces a new dryRunModethat enables a simplified pipeline configuration for testing and debugging purposes.

• Added dryRunMode to the collector CRD.
• Implemented a CEL validation rule that enforces that dryRunMode can only be enabled when debug is also set.

When dryRunMode is enabled:

• Only data-modifying components are included in the generated pipeline (e.g., transform processors, k8sattributes processor).
• All exporters except the debug exporter are disabled.
• Persistence options are disabled.

This feature is particularly useful for:

• Testing new processor configurations in isolation.
• Validating data transformations before production deployment.
• Debugging telemetry pipelines without affecting production exporters.

[pepov]

debug and debugMode can be confusing at first. why not just use debug and put all these feature behind a single flag? if it makes sense to control for example persistence separately, I would add a flag for that specifically

[csatib02]

@pepov

Persistence is controlled by a single flag on tenant's level.

The power of debug-mode is to have a hassle free method for testing out the whole pipeline without having to worry about which components to enable/disable to have no side-effects.

The current validation layer catches all syntax errors before deploying, but runtime errors/misconfigurations such as invalid/not at all working ottl statements, might not show up at all.

[pepov]

Still not sure why we need both debug and debugmode flags at the same time

[csatib02]

Debug, essentially adds a debug exporter next to the configured ones, it also raises the log level of all components to debug.

[csatib02]

I've changed the naming from debug-mode to dry-run mode.