Update CI for new spec-parser output

[zvr]

@bact a heads-up!
The spec-parser now outputs the generated files in a different directory structure.

If it is run via
python3 /some/dir/spec-parser/main.py /somewhere/spdx-3-model/model /generate/outputdir

it will generate outputdir and its contents will be:

.
├── diagram
│   └── model.plantuml
├── jsondump
│   └── model.json
├── mkdocs
│   ├── AI
│   │   ├── AI.md
│   │   ├── Classes
│   │   │   ├── AIPackage.md
...
├── model-files.tex
├── model-files.yml
├── rdf
│   ├── spdx-context.jsonld
│   ├── spdx-model.dot
│   ├── spdx-model.json-ld
│   ├── spdx-model.pretty-xml
│   ├── spdx-model.ttl
│   └── spdx-model.xml
└── tex
    ├── AI
    │   ├── AI.tex
    │   ├── Classes
    │   │   ├── AIPackage.tex
...

Note the new location for everything RDF (the ontology as well as the context) and new names for files list (to be included in the mkdocs configuration) and generated md files.
Also note that the files list uses the old top-level directory name. If the tree is not copied, I can be easily change this in spec-parser.

[bact]

@zvr Thank you for a very detailed info. I will adjust accordingly.

[zvr]

@bact any progress on handling this one?

The sooner it's ready, the sooner I can merge the changes to spec-parser, so that further collaborative development can be done (since I've notices a couple of issues raised by @goneall there).

[bact]

The propose change is in #1100 but it still using the old structure since it's relying on the current spec-paser - as if it uses the new dir structure, it will not pass the checks.

Once spec-paser merges the changes, we can:

1. pause updates in spdx-spec rep
2. update Line 22-23
3. run the CI
4. unpause the updates in spdx-spec repo

[bact]

Btw, if we like to keep the old structure of pre-3.0.1 publication, we may need to update publication workflow in development/v3.0 branch to use a specific version (commit hash, release tag, etc) of spec-parser before the dir changes.

Or, alternatively, modify the development/v3.0 workflow to copy files from new dirs to old dirs.

[zvr]

OK, do we want to do a synchronized update?

[bact]

OK, do we want to do a synchronized update?

@zvr When #1100 got another approval (to make it two approvals), I think we are good to go.

[zvr]

Thanks, @bact. I'll probably merge bith #1100 and the new spec-parser later today or early tomorrow, so we have time to fix any issues that arise before the weekend.

[bact]

Thank you. I will standby.

[bact]

Note, #1113 is now using this new structure