Feat: apply ord document validator in CICD pipeline

[zongqichen]

At the moment, we only have unittest to protect the result of ord default content generation. However, we need to validate the correctness of ord content by validator.

[Fannon]

In some other projects, I added the API Metadata Validator as an NPM dependency. Then you can call the validator programmatically (not as CLI) in your unit-tests. This will give you a better, integrated testing experience.

[zongqichen]

We also need to solve: #63 (comment)

[aramovic79]

In some other projects, I added the API Metadata Validator as an NPM dependency. Then you can call the validator programmatically (not as CLI) in your unit-tests. This will give you a better, integrated testing experience.

I remember that the recommended way of running the MetadataValidator was by using docker image.
Public Artifactory: cpa-docker.common.repositories.cloud.sap/api-metadata-validator:latest
Internal Artifactory: cpa-docker.cpa-docker.int.repositories.cloud.sap/api-metadata-validator:latest

Has the recommendation being changed meanwhile?
I think we should decide which way is more reliable(and faster also): to run Jest tests by using, as you wrote, API Metadata Validator package or by running API Metadata Validator docker image.

[swennemers]

waiting for open source release of api metadata validator