Veraltete Links bei Schemavalidierung
### Description of the bug:
Fitko Seite zur Schemavalidierung (
https://docs.fitko.de/fit-connect/docs/getting-started/schema-validation/
) ist uns aufgefallen, dass die Links zur Schema-Validatoren und Code-Generatoren veraltet sind diese müssten wahrscheinlich auf json-schema.org/tools verweisen
### Current behavior:
<!-- Describe here what actually happens when the bug occurs -->
### Expected behavior:
<!-- Describe here what is actually expected if the bug does not occur -->
### Environments:
<!-- Specify here which environments are affected, e.g. DEV, TEST, STAGE, PROD -->
### Additional Information:
<!-- Enter further relevant information here, e.g. operating system, browser etc. including the version of the FIT-Connect component -->
### Dependency / relationship to other issues:
<!-- Write down here what kind of relationship it is and a brief explanation of it. -->
### Responsible person / team:
<!-- Insert here the name of the person or team responsible for processing the bug. -->
### Contact persons including contact details:
<!-- Indication of contact persons such as the person who reported the error, how to reach them. -->
### Screenshots / Logs / Requests:
<!-- Insert screenshots or other (visual) aids here if necessary to clarify the bug. -->
### Checklist:
- [ ] Add Severity label
- [ ] Add team label
- [ ] Related/affected issues/stories/epics linked and explained in the bug issue
- [ ] Creation of an automated test
- [ ] Bugfix deployed on DEV
- [ ] Bugfix tested on DEV
- [ ] Bugfix deployed on TEST
- [ ] Bugfix tested on TEST (possibly also by the connection project itself)
- [ ] Successful fix reported to Team Operations (Teams channel)
- [ ] Bugfix deployed on STAGE
- [ ] Bugfix tested on STAGE if necessary
- [ ] Bugfix deployed on PROD
- [ ] Bugfix tested on PROD (possibly also by the connection project itself)
- [ ] Final communication by Team Operations if necessary
- [ ] Internal documentation was checked and updated if necessary
- [ ] External documentation has been checked and updated if necessary
- [ ] Updated changelog if necessary
### Approach/Solution:
<!-- Other comments or notes can be added here, e.g. what has been tried so far to solve the problem. -->
### Release version of the artifact:
issue