Setup sync with AK

[uittenbroekrobbert]

Description

The Algoritmekader is (now) the source of truth for lifecycles, roles, labels, measures and requirements. This PR adds a sync script which fetches the AK and transforms the data into a format AMT can use.

The Sync script can either sync the data or output a diff report. This script will run daily so we can act on changes in the AK.

Resolves #69

Checklist

Please check all the boxes that apply to this pull request using "x":

• I have tested the changes locally and verified that they work as expected.
• I have followed the project's coding conventions and style guidelines.
• I have rebased my branch onto the latest commit of the main branch.
• I have squashed or reorganized my commits into logical units.
• I have read, understood and agree to the Developer Certificate of Origin, which this project utilizes.

[laurensWe]

Maybe not for this ticket, but how would we go about managing versions? If there is a diff then it could be because the version is different of the specific vereiste but then if the name is different that would now mean a new vereiste with a new URN

[anneschuth]

couple of questions

[anneschuth]

Do I understand correctly this will keep alerting us of a diff until we update files in this repo?

Is there a mechanism to update them manually?

(The above was already answered here: #69 (comment))

Once we start versioning the files we're checking/producing, I suppose we should make sure that we're checking against the latest version of these files

[uittenbroekrobbert]

Maybe not for this ticket, but how would we go about managing versions? If there is a diff then it could be because the version is different of the specific vereiste but then if the name is different that would now mean a new vereiste with a new URN

Versioning is out-of-scope for this ticket. Peeking forward, versioning probably will be a delicate puzzle, deciding whether changes are 'patch, minor or major' and what implications that may have in AMT as well.

[berrydenhartog]

LGTM

[uittenbroekrobbert]

Do I understand correctly this will keep alerting us of a diff until we update files in this repo?

Is there a mechanism to update them manually?

(The above was already answered here: #69 (comment))

Once we start versioning the files we're checking/producing, I suppose we should make sure that we're checking against the latest version of these files

AK said they tag their releases, which can be considered the 'latest version' and the sync script retrieves the tags and determine which is latest, so, this should work, in theory.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud