chore: add query-frontend option to select request headers in query logs

[jmichalek132]

What this PR does:

Adding feature present in mimir and Loki, specifically grafana/mimir#5030 and grafana/loki#11422.

Adds a config option to the query-frontend to specify a list of request headers to include in query logs.

For example, setting -query-frontend.log-query-request-headers="X-Grafana-Org-Id" and sending a query with X-Grafana-Org-Id:1 results in query log lines that include header_x_grafana_org_id=1.

Which issue(s) this PR fixes:
Fixes #3342

Checklist

• Tests updated
• Documentation added
• CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

[CLAassistant]

All committers have signed the CLA.

[jmichalek132]

For the pipeline failure, the test fails looks unrelated to my change:

tenant=0 component=remote level=info remote_name=ce2f78 url=http://127.0.0.1:35569/receive msg="Scraped metadata watcher stopped"
    instance_test.go:140: 
        	Error Trace:	/home/runner/work/tempo/tempo/modules/generator/storage/instance_test.go:140
        	            				/home/runner/work/tempo/tempo/modules/generator/storage/instance_test.go:340
        	            				/opt/hostedtoolcache/go/1.21.6/x64/src/runtime/asm_amd64.s:1650
        	Error:      	Received unexpected error:
        	            	write /tmp/TestInstance_multiTenancy3811487438/001/0/wal/00000000: file already closed
        	Test:       	TestInstance_multiTenancy
tenant=0 component=remote level=info remote_name=ce2f78 url=http://127.0.0.1:35569/receive msg="Remote storage stopped."

For the linting I ran make lint locally as instructed by the contributing guide, but it came up with many complaints for code I didn't touch, so unsure how to address that.

[mapno]

LGTM, only to minor things.

[joe-elliott]

For the pipeline failure, the test fails looks unrelated to my change:

Don't worry about this. CI flakiness. We can ignore this error.

[mapno]

LGTM. Thanks!

[mapno]

Ups, it seems the logQueryRequestHeaders wasn't correctly updated everywhere. When that's fixed I'll merge cc/ @jmichalek132

[jmichalek132]

Ups, it seems the logQueryRequestHeaders wasn't correctly updated everywhere. When that's fixed I'll merge cc/ @jmichalek132

Sorry for the delay, fixed now.