Replace internal links between ICM documents with relative links to stay within the same release tree / fork / release package

[hdamker]

Problem description

documentation/CAMARA-API-access-and-user-consent.md contains about six links to the Profile document which are written as fully qualified URLs which are pointing to the main branch of ICM. The Profile contains one such link which points to documentation/CAMARA-API-access-and-user-consent.md

A reader within a release tree would jump out of the tree into a potential wrong version. The same for someone who has downloaded the release package (zip-file) of ICM.

Expected behavior

Use - as recommend by GitHub - relative links instead, concrete with the following replacements:
https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/documentation/CAMARA-Security-Interoperability.md to be replace with CAMARA-Security-Interoperability.md
https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/documentation/CAMARA-API-access-and-user-consent.md to be replaced with CAMARA-API-access-and-user-consent.md

Alternative solution

Additional context

[hdamker]

@jpengar @AxelNennker If you agree, could someone of you take the PR for this issue?

[jpengar]

Let's talk about it in Today's call. I could easily do it in #181.

[hdamker]

It would be cleaner to do it in a short separate PR ... otherwise you have no PR you can mention in the Changelog ;-)

[jpengar]

It would be cleaner to do it in a short separate PR ... otherwise you have no PR you can mention in the Changelog ;-)

xD I can do that too

[hdamker]

xD I can do that too

Created #188 a few seconds before your comment :-)