Proposed title of this feature request
Improve validation of tracing object storage secret

What is the nature and description of the request?
Installing Tracing, at the moment of creating the object storage secret [0], if it's set by error inside the secret the "region" field, it's received an error like:

The TempoStack "instance" is invalid: spec.storage.secret.name: Invalid value: "tempo-s3": storage secret contains fields for long lived and short lived configuration

This error is not clear about where the problem really is and also for the error is prone to guide in the wrong direction.

It's requested a better validation - message when a non expected field is present in the tracing object storage secret.

Why does the customer need this? (List the business requirements)

Reduce resolution time.

List any affected packages or components.
Tracing

[0] https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html/distributed_tracing/distr-tracing-tempo-installing#distr-tracing-tempo-object-storage-setup_distr-tracing-tempo-installing