Add requirements and measures to task registry client

[ChristopherSpelt]

Description

Fetch requirements and measures from task registry

• Created a TaskRegistryAPIClient which extends a base APIClient to make requests to the task registry.
• Since logic for fetching tasks (instruments, requirements and measures) is similar created a TaskRegistryRepository which fetches tasks. It is not intended to be used explicitly on its own, but rather it is injected in the services InstrumentService, RequirementService and MeasureService.

Functionality to filter requirements and measures based on AI Act Profile outcomes

• An async function get_requirements_and_measures returns the requirement and measures according to an AI Act Profile.

NOTE THE FOLLOWING:

• publication_category is now renamed to risk_category. The logic for handling this is not very pretty but is necessary because existing algorithms (projects) in the database already have system card JSON's with the key publication_category in them.
• Renaming of fields and values in instruments, requirements and measures can now have consequences for AMT.
• Certain pages now load more slow due to the fact a lot of network requests are made to the task registry. We need to consider good caching strategies.

Resolves #323

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.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
1 Accepted issue

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

See analysis details on SonarQube Cloud

[berrydenhartog]

LGTM