fix(traceql): fix extract matcher regexes to work with regexp-type matchers

[sd2k]

This improves the regexes used by autocomplete (and I think the search tags v2 endpoint?) so that they work with queries like { resource.service.name = "app" && resource.k8s.cluster.name=~"prod-.+" }.

Fixes #3635.

[CLAassistant]

All committers have signed the CLA.

[joe-elliott]

unsure why the drone CI failed. I have restarted it.

can you sign the CLA and add a changelog entry?

[sd2k]

Hmm I've rebased on main just in case. Signed the CLA and added a changelog entry too 👍

[mdisibio]

Drone is failing on the step to test the debian package because tempo isn't starting up. It doesn't seem like it captures the tempo logs. Unlikely to be caused by the changes in this PR, but digging into it.

[mdisibio]

I wasn't able to do exact reproduction of the drone steps because of systemd-in-docker woes, but was able to confirm that make release-snapshot builds the deb, it installs, and the included tempo binary starts ok with /usr/bin/tempo -config.file /etc/tempo/config.yml. Leaning towards bypassing the drone step and merging.

level=info ts=2024-05-08T12:36:44.545535434Z caller=main.go:118 msg="Starting Tempo" version="(version=2.4.0-SNAPSHOT-1539758b9, branch=3635-autocomplete-regex-issues, revision=1539758b9)"
level=info ts=2024-05-08T12:36:44.548547946Z caller=server.go:240 msg="server listening on addresses" http=[::]:3200 grpc=[::]:9095
...
level=info ts=2024-05-08T12:36:44.623156247Z caller=app.go:214 msg="Tempo started"

[mdisibio]

The drone issues were resolved in #3657 and all looks good. Thanks.