Individual URIs for Suites

Currently the Research Software Ecosystem imports tools (suites) metadata from the [tools.json](https://raw.githubusercontent.com/galaxyproject/galaxy_codex/refs/heads/main/communities/all/resources/tools.json) file.

As for individual tool URIs, we use the prefix `https://github.com/galaxyproject/tools-iuc/tree/master/tools/`. Is it still right?

I see that some suites have other repositories as sources and don't seem to be in the `tools-iuc` folder (ex. askor_de). Those sources are in the fields "Suite source" and "Suite parsed folder". Those are sometimes different, and "Suite source" is sometimes `null`. Is it OK to use the field "Suite parsed folder" as a URI? Is it stable?

@scorreard @paulzierep @supernord

Review tools.json and the askor_de example, comparing the "Suite source" and "Suite parsed folder" fields with the existing individual-tool URI prefix. Determine and validate a stable URI convention for suites across the listed cases; done means the convention is agreed and consistently applicable.

Written by the indexing model from the issue text.