Table schema: Foreign Key constrains information could be enhanced.

[jh-RLI]

Description of the issue

We introduced the "topics" key as list for all schemas/topics a table is available at on the OEP. We do not use this approach when referencing a Foreign key table

oemetadata/oemetadata/v2/v20/example.json

Line 322 in 5e435ab

"resource": "model_draft.oep_oemetadata_table_example_version",

Ideas of solution

To make the usage of topics consistent, we could introduce a "topic" key which is not a list of topics but expects a string with the topic name where the FK table is available at.

Workflow checklist

• I am aware of the workflow in CONTRIBUTING.md