Remove or update GHA build

[strogonoff]

There is a left-over GHA workflow that rebuilds concept database YAML from XLSX.

I believe this no longer applies as it is now, since we’re switching to production and an update could overwrite changes made through the app.

• This could still be done manually instead of via GHA

• The GHA build could be updated so that, instead of overwriting the full YAML structure with migrated XLSX data, it modifies the existing YAML. For example, if something changed in XLSX for an existing entry, it could add an automated revision (under the name, e.g., “Glossarist bot” or “Geolexica bot”) for it.

(I believe I might have removed this workflow before, but forgot to do it again when I had to re-create my PR after repo went public and fork connection was lost.)

[strogonoff]

@ronaldtse Do you think we can expect occasional changes coming via XLSX during the initial post-Glossarist-transition period?

[ronaldtse]

We won't run the XLSX anymore. Translations that come in via Excel should be manually migrated. Unless we have some "CVS import => new CR" functionality...

[skalee]

Neither I see any reason to keep legacy workflows. That said, it seems reasonable to do some integrity testing in GHA, although I have no idea what these tests could look like. Also, we may consider some brand new release workflow (see https://github.com/geolexica/isotc211.geolexica.org/issues/141).