feat(ipa): add IPA-132 OperationResponse schema rules

[julius-jogela]

Proposed changes

This PR adds the IPA-132 rules validating how long-running operation status is communicated through the OperationResponse schema. Stacked on #1435; the base retargets to main once that merges.

Jira ticket: CLOUDP-429837

Rules added

All at warn severity:

Rule	Guideline	Checks
xgen-IPA-132-operation-endpoints-must-return-operation-response	IPA-132-operation-endpoints-must-return-operation-response	The single Operation endpoint (.../operations/{operationId}) must reference the OperationResponse schema; the Operations collection endpoint must return a paginated response whose results items reference it. Exceptions at the content media type level
xgen-IPA-132-operation-status-must-use-the-standard-status-enum	IPA-132-operation-status-must-use-the-standard-status-enum	OperationResponse must define a status property whose enum is exactly PENDING, IN_PROGRESS, SUCCEEDED, FAILED, CANCELED, SUPERSEDED
xgen-IPA-132-operation-response-must-include-core-metadata	IPA-132-operation-response-must-include-core-metadata	operationId, operationType, createdAt, updatedAt defined and required; operationType enum exactly CREATE, UPDATE, DELETE, CUSTOM; customMethod defined but not required (it applies only to CUSTOM operations, which cannot be validated statically)

The schema rules anchor on $.components.schemas.OperationResponse per the guideline metadata. The OperationResponse schema name, both enums and the exact-enum-match helper live in utils/longRunningOperations.js for reuse by the remaining IPA-132 rules.

Testing

• 25 new tests: every Correct/Incorrect example from the IPA-132 guidelines is a test case, plus per rule a violation-with-exception (suppressed) and adoption-with-exception (flagged as unnecessary) case, and unit tests for the enum helper.
• Full suite: 122 suites / 758 tests pass. gen-ipa-docs, prettier and eslint clean.
• spectral lint openapi/.raw/v2.yaml with the full ruleset: 0 xgen-IPA-132-* findings — the spec defines no OperationResponse schema yet.
• Live-fire check: a complete compliant LRO spec produces 0 findings across all six IPA-132 rules; planting a non-standard enum value, dropping a field from required, and de-referencing the schemas each fires exactly the right rule.

Checklist

• I have signed the MongoDB CLA
• I have added tests that prove my fix is effective or that my feature works

Changes to Spectral

• I have read the README file for Spectral Updates