Define logic for suits with tools that have different bio.tools entries

Currently, we assume that all tools in a suite (i.e. github folder) have the same bio.tools ID.
However, there are some suites where the contained tools have different bio.tool IDs: For example: https://github.com/galaxyproject/tools-iuc/tree/main/tools/spades

As a consequence, our tool only parses one bio.tools entry, which is not correct for all tools.
We need to brainstorm how to handle these cases.

A) Aggregate the bio.tools entries and EDAM Terms (similar to the `Galaxy tool ids` row)
B) One row for each Galaxy tool ids (this would probably mean a good amount of restructuring, i.e. creating a tool list and an aggregated list)

Any vote for either way ?