Proposed semconv pre-release process

[chalin]

@trask - great work on getting the 1.30.0 release out! 🙌🏻 🎉

I think that open-telemetry/opentelemetry.io#6077 is somewhat typical of new semconv release PRs. Inevitably issues arise, such as the following, and we end up doing double the work (fixing semconv and patching OTel.io):

• Fix links #1814
• [editorial] Alias needs to be changed for renamed docs file #1815

@trask and I have been working on improving the release process. @trask created a daily build script. That allowed us to catch some issues ahead of the new release, such as:

• [docs] incomplete <-- toc --> directive #1799
• [editorial] Fix alias in general/trace.md #1805

I think that the best way forward is to open a PR over OTel.io and incrementally (maybe daily) update the semconv repo version used by that PR. If any issues arise, then an @open-telemetry/docs-maintainers can fix them and push changes to the PR. The PR also give us the ability to preview the semconv release.

(That's what I did with open-telemetry/opentelemetry.io#6060, which built without any issues. The problem is that more updates were applied to the semconv repo, and not retested.)

Thoughts @trask @lmolkova et all?

[trask]

ya, that sounds like a better way to go 👍

I'm going to start working on some automation for it