Alignment with Commonalities r3.3

[albertoramosmonagas]

What type of PR is this?

Add one of the following kinds:

• documentation

What this PR does / why we need it:

• ErrorInfo schema unified with CAMARA_common.yaml and event-subscription-template.yaml → reordered required fields, clarified message, status, and code descriptions.
• Updated mandatory description for date-time string format in template files.

Which issue(s) this PR fixes:

Fixes #32

Special notes for reviewers:

Nothing relevant, everything comes from the latest changes in commonalities.

Changelog input

 release-note
Alignment with Commonalities r3.3 – unified ErrorInfo schema (fields reordered, clarified descriptions for message, status, and code) and updated mandatory description for date-time format.

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
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	secretlint	yes		no	0.57s
✅ YAML	yamllint	1		0	0.36s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[Copilot]

Pull Request Overview

This PR aligns the predictive connectivity data API specification with CAMARA Commonalities r3.3 standards. The changes focus on standardizing error schemas and date-time field descriptions to maintain consistency across CAMARA API definitions.

• Updated ErrorInfo schema to match common CAMARA structure with reordered required fields and clarified property descriptions
• Standardized date-time field descriptions to reference RFC 3339 instead of ISO-8601

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}