OTEL Traces for Database interactions should only optionally include values

[endocrimes]

Database queries often contain potentially sensitive data (PII, credentials/api tokens, ...), currently, Spin will always send those values to OTel (example from a sqlite database):

This would be a compliance or security issue in some contexts, so ideally we should only do this if a developer opts in for further debugging support (in local/dev envs). Or never emit those values (and instead just include types or similar).