feat(5434): extend content type schema coverage and validation in integration tests

[OMpawar-21]

feat(test): deepen content type schema integration coverage and validation paths

Content type integration tests now stress a wider range of schema shapes and API
behaviors against the Management API.

Schema and fixture coverage

• Simple JSON-driven content types (basic text fields) for disposable create/fetch/
  update/query/delete flows, including pagination on list endpoints.
• Medium and complex fixtures: nested groups, repeatable groups, modular blocks,
  RTE and JSON RTE-style fields, and common scalar types (number, select, date,
  image, etc.) with structure assertions after round-trip fetch.

Cross-cutting field types

• Custom field extensions: upload an extension, reference it from an ExtensionField
  on the schema, and verify extension_uid on fetch.
• Taxonomy: create a taxonomy, bind it via a TaxonomyField on the content type
  schema, and assert bindings after fetch (sync and async).

Negative / error paths

• Invalid or duplicate UIDs, missing title, and operations on non-existent content
  types (create, fetch, update, delete) with expected API error handling.
• Schema-level failures where taxonomy or extension UIDs do not exist on the stack.

Legacy stack types

• Existing single-page / multi-page content type flows remain as separate tests
  (create-or-fetch, update with shared schema JSON, query) alongside the expanded
  suite.

Notes

• Tests are integration-level and require valid stack credentials and environment
  configuration. Adjust allowed HTTP status codes if the API returns alternate
  codes for the same scenarios.

The merge-base changed after approval.

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	0	0	10	✅ Passed
🟠 High Severity	0	0	25	✅ Passed
🟡 Medium Severity	0	0	500	✅ Passed
🔵 Low Severity	0	0	1000	✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	0	90 / 365 days	✅ Passed
🔵 Low	0	0	180 / 365 days	✅ Passed

✅ BUILD PASSED - All security checks passed