Share TraceQL page

[jdbaldry]

What this PR does:
Prepares the TraceQL index page for being reused in other projects with the docs/shared shortcode.

It uses the relref shortcode to get build time link checking including the links to Loki.
The behavior is not perfectly correct given that it checks for pages in the most recent commit of Loki rather than the actually released content but I think this is still a step forward over blind linking.

The make docs target is updated to use the centralized make-docs script from Writers' Toolkit.
The script makes it easy to build multiple documentation sets together, even at specific versions if required.
For now, it only concerns itself with building Loki and Tempo side-by-side for relref link checking.

Things for reviewer to check:

1. You can run make docs
2. You can see all the images in pages under http://localhost:3002/docs/tempo/latest/traceql/
3. You can navigate to all links (including to the Loki docs!)
4. Maybe run doc-validator on the traceql/_index.md file with make doc-validator/traceql/_index.md

Commits:

• Move traceql to shared directory

• Add 'Grafana Cloud' and 'Enterprise' labels to TraceQL

• Use relrefs for docs links, partial URIs for blog links

• Update Makefile to support cross repository docs builds

• Clean whitespace

• Prefer "preceding" over "above"

• Prefer one line per sentence for better line based diffing

• Use object storage for traceql image assets

• Try building multiple documentation sets in CI

[knylander-grafana]

Thanks for doing these updates! Preview build looks clean.

[knylander-grafana]

@jdbaldry I just tried deleting my local clone of the Loki repo and make docs failed because the repo wasn't found.

Would this change mean that any one who tries to build Tempo docs will have to have the Loki repo cloned locally as well?

Does this also tie Tempo docs to Loki docs? If there is an error in the Loki docs, does that mean the Tempo docs won't build?

[jdbaldry]

Would this change mean that any one who tries to build Tempo docs will have to have the Loki repo cloned locally as well?

You can override the required projects by running make docs PROJECTS=tempo.
That only builds tempo by itself.

Does this also tie Tempo docs to Loki docs? If there is an error in the Loki docs, does that mean the Tempo docs won't build?

Critical errors in Loki or Tempo docs will break local builds but broken links will appear as warnings just as before.