Use GH API to collect versions from remote test harnesses

[OptimumCode]

The PR adds a collection of version information from remote test harnesses. It collects all available version tags (like harness-release-*), plus it uses the latest tag to get the latest available test harness version.

Related to #1849

---

📚 Documentation preview 📚: https://bowtie-json-schema--1916.org.readthedocs.build/en/1916/

[Julian]

@OptimumCode what did we leave off on here? I'm sure it's my fault that this PR stalled (really sorry!) if you have a moment let me know what I needed to do here (was it just it's ready for a final review / merge)?

[OptimumCode]

It is not your fault @Julian ) The actions are on my side - I need to modify the workflow in the harness repository so it does not generate tags like vv1.2.3 and modify this workflow to do the same (in case of latest tag). I have recently switched jobs and cannot find a time to finish that yet, unfortunately... Hopefully, I will find time in a few weeks...

Re PR itself, I think it will be ready for review once I (or somebody else) complete the above actions (if we are okay to keep current logic that collects tags until #1928 is implemented).
After that, it looks like this is the final step after which we can proceed with migration of other harnesses (create template repo with workflows and configs and start moving harnesses to separate repos)

[OptimumCode]

After the following change (bowtie-json-schema/kotlin-kmp-json-schema-validator#20), the tag for the test harness will start with a harness-release- suffix. That should reduce the chance of collision with user-defined tags and with implementation versions that start with v

[OptimumCode]

The PR is ready for review now. Could you please take a look, @Julian, once you have time?

[Julian]

I haven't tried to run this, just glanced at it, but if you've run it and it works this is good to merge with me. Just left 2 minor comments.

[OptimumCode]

Thank you, @Julian! I have ran it partially, will try to run the whole workflow and if all is good, I will merge the changes. I will do that closer to the end of the week (and make changes according to your comments)

[OptimumCode]

Hi @Julian, I have tried to execute the whole workflow locally, and it looks like I am missing something because I am getting an error on the following command:

mkdir "$impl/v$version" # when dialect.json is created for each version

mkdir: kotlin-kmp-json-schema-validator: Not a directory

A few lines above, we copy the matrix version file to the current dir with the name equal to the implementation name

cp $MATRIX_VERSIONS_FILE $impl

Now, we have a file with the implementation name, and because of that, we cannot create a directory with the same name. But I don't see any errors in the workflow execution on GitHub, meaning it works okay there. Have you happened to know how it works on GitHub runner? Maybe we should correct the script a bit so we can execute the same code locally if needed?

[OptimumCode]

Hi, @Julian! Just wanted to check if you had a chance to take a look at my last comment. I think this uncertainty is the only thing that blocks from merging the PR (because I honestly have no idea how it works right now on GitHub, and don't want to break anything since I was not able to run the workflow completely)

[Julian]

I saw it but I didn't have any idea either without trying it out myself :) at a first glance you looked right but as you say it works here so clearly we're misreading the shell code and it's doing something slightly different (which is why I always want to get rid of it and exchange it for working and tested Python code)

I don't know when I'll get a chance to run it myself, I have a huge number of things on my plate to get to -- I'd say if it's not obvious to the two of us but works here it's possibly still fine to merge, as we must be missing something simple...

[OptimumCode]

Agree, let's wait until weekend - I will merge the changes and try to execute the updated workflow. If something doesn't work - I will prepare a PR with fix

[Julian]

Sounds great, thanks again for all your hard work!

[OptimumCode]

I forgot I have a day off today) I have found a small issue and fixed it in #2020. The rest looks pretty good - I can see the trends chart for external test harness (https://bowtie.report/#/implementations/kotlin-kmp-json-schema-validator).