Add a tool that allows us to quickly update specification URLs to a s…

[jsuereth]

…pecific version.

This should make it a lot easier for us to direct link against the specification and rapidly update links/check them over time.

[Oberon00]

Note that there is an issue for that at the semantic convention generator: open-telemetry/build-tools#20 But since this is now needed also outside the generated markdown, a separate tool might be better anyways. Do consider adding it to the build-tools repository though (or should the semconv generator move here?)

(As long as it's only a short shell script like this, it doesn't really matter though)

[jsuereth]

@Oberon00 very good questions. I like to start small and evolve over time, so I think since the script is short and directly tied to semconv maintenance, we can leave it here.

If we discover limitations that necessitate moving it into build-tools I'm more than happy to move the tool over there.

Regarding the evolution of build-tools and this repository, it COULD be we merge them together over time. Let's see how "momentum" goes as we migrate to this new repository and if we find huge friction keeping it separate then we can push for merging.

It's a great call out, let's have everyone keep the idea on our radar.

[Oberon00]

I like the find solution, however, I wonder if we should add a check against adding files with spaces to the repository instead of trying to support spaces here. You probably don't want paths with spaces anyways, and somewhere you most likely will run into a bug anyways.

[jsuereth]

Thanks for the improvements!

Regarding spaces in files, remember that's common in windows that your home directory may even have spaces. When using WSL / cygwin, it's really important to handle regardless.