Issue #4 requested changes

[jpengar]

What type of PR is this?

• enhancement/feature

What this PR does / why we need it:

This pull request updates the consent management API definition to improve consistency, clarity, and error handling regarding consent text information. The most significant changes include standardizing the naming of the consent text field, introducing a new field to track consent text updates, and refining error response handling for invalid consent text IDs.

• [Typo] Renamed the ConsentText field to consentText throughout the API specification, including all schema definitions, response examples, and documentation, to ensure consistent use of camelCase.
• Added a new optional lastUpdate field to the consentText object, allowing API providers to specify when a consent text version was last updated. This is reflected in the schema, documentation, and all relevant response examples.
• Introduced a new Consent400 error response for 400-level errors specific to consent text validation, including a new error code CONSENT_MGMT.INVALID_CONSENT_TEXT_ID for cases where an invalid or non-existent consentTextId is provided. Updated the relevant API path to reference this new error response.

Which issue(s) this PR fixes:

Fixes #4

Special notes for reviewers:

N/A

Changelog input

Enhancements & error corrections

Additional documentation

N/A

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	2		0	0.01s
✅ API	spectral	1		0	1.54s
✅ REPOSITORY	git_diff	yes		no	0.0s
✅ REPOSITORY	secretlint	yes		no	0.59s
✅ YAML	yamllint	1		0	0.42s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[sebdewet]

LGTM