chore(loki): default query settings, config as secret

[mjnagel]

Description

• Updates to the same defaults for loki as are used on our staging test clusters (better experience querying logs)
• Switches to a secret for the config rather than configmap (note that aws access keys end up in this configmap today if not using IRSA)
• Cleans up some unnecessary values on tokengen (disabling sidecar, legacy BB values based on job termination issue)

Related Issue

N/A

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Test, docs, adr added or updated as needed
• Contributor Guide followed

[MxNxPx]

Description

• Updates to the same defaults for loki as are used on our staging test clusters (better experience querying logs)
• Switches to a secret for the config rather than configmap (note that aws access keys end up in this configmap today if not using IRSA)
• Cleans up some unnecessary values on tokengen (disabling sidecar, legacy BB values based on job termination issue)

Can confirm that these changes to the loki values fixed query issues we were experiencing.

            # Ensure we don't hit query limits
            - path: loki.limits_config.split_queries_by_interval
              value: "30m"
            - path: loki.query_scheduler.max_outstanding_requests_per_tenant
              value: 32000 # This is the new default in Loki 3.0
              ```