URNs, Links, Templates, Schema, Defaults

[anneschuth]

In this PR I introduce a few changes to the instrument registry format by changing the example iama.yaml.

• Move to urns (instead of IDs)
• Move to links being lists of objects (instead of strings)
• Move to system card templates to make it clear why answers even appear
• Use 'open_question' instead of 'open question' as a task type
• Remove measures folder (leftover)
• Formatted the yaml file
• Introduced a proper schema and schema validation
• Adds all defaults from MinBZK/python-project-template

[GuusjeJuijn]

Should we also adjust the json schema according to this new link structure?

[GuusjeJuijn]

Looks good! 👍

[anneschuth]

@GuusjeJuijn I've added a proper schema and schema validation as well

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[ChristopherSpelt]

Just one small comment, but looks very good!