Alignment of API definitions with Commonalities r3.3

[hdamker]

What type of PR is this?

• Enhancement

What this PR does / why we need it:

• reset version in YAML files to wip (intentionally not done for the .feature files to limit merge conflicts)
• cherry-picked f3d400a from Public r3.2 - M4 - Fall25 #229
• reverted the order of ErrorInfo properties back to the one defined in API Design Guide (see issue New ErrorInfo schema alters the expected properties order Commonalities#515) to keep the order in line with the examples

Merging this PR and update #229 with main afterwards will eliminate most of the changes from the release PR which are not belonging there, but there will also the need to resolve some conflicts. Happy to help with that.

Which issue(s) this PR fixes:

Fixes # no issue created, but see #229 (comment)

Special notes for reviewers:

I assumed that the content of f3d400a, as already reviewed in #229

Changelog input

 Alignment with latest changes of Commonalities in release r3.3

Additional documentation

This section can be blank.

docs

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	2		0	0.02s
✅ OPENAPI	spectral	2		0	3.34s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	secretlint	yes		no	0.78s
✅ YAML	yamllint	2		0	0.55s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[bigludo7]

LGTM

[hdamker]

@bigludo7 don't forget to delete the branches, especially if they are within the upstream repository.

[bigludo7]

@bigludo7 don't forget to delete the branches, especially if they are within the upstream repository.

Sure ! I deleted them when I'm the author usually :) - I will deleted this one.