Sync common files from Commonalities r4.2

[camara-release-automation]

Automated sync of code/common/ files from camaraproject/Commonalities at release tag r4.2.

This PR was created by release automation because the cached Commonalities files were out of sync with the declared dependency in release-plan.yaml.

What changed:

• Updated files in code/common/ to match Commonalities r4.2
• Added/updated .sync-manifest.yaml with file integrity hashes

Action required: Review and merge this PR. The /create-snapshot command will be blocked until common files are in sync.

[camara-validation]

CAMARA Validation — PASS

0 errors, 21 warnings, 8 hints | Profile: standard

View full results

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	4		0	0.01s
✅ API	spectral	1		0	2.16s
✅ GHERKIN	gherkin-lint	3		0	1.21s
✅ REPOSITORY	git_diff	yes		no	0.02s
✅ REPOSITORY	secretlint	yes		no	0.88s
✅ YAML	yamllint	1		0	0.62s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[hdamker]

The validation has found 4 errors within the code on the main branch of the repository. 3 of them are false positives (the rule looked only into the first line of the .feature files, not into the first line which starts with "Feature: ...". I have opened camaraproject/tooling#248 for that. As soon fixed, these errors will go away. I will come back when done.

The remaining one is a one line fix (adding the appropriate type field. You can either fix it here in the PR before merging or do a separate PR before or after the merge.

[hdamker]

Fixed the missing type error within the CommonResponseBody schema with 7a6b323. Main purpose was to trigger the Validation check on a fresh commit. The three false positives are gone (due to the fix camaraproject/tooling#249 which is now part of Validation@v1-rc).

As expected now down to 0 errors. I haven't touched the warnings and hints.

If you don't want to have the fix on this sync PR itself and want to fix it in a separate PR, just close this PR and run the Release Automation workflow within the Actions tab once. It will create a new sync PR.