Updated postman collection as per Enhance Gateway Key & Certificate Management lifecycle

[DamandeepToor]

F162647: Enhance Gateway Key & Certificate Management lifecycle.

This PR adds graphman-client support for the new certificate and key runtime validation status APIs introduced in Gateway v11.2.2.

Changes

Postman Collection (postman/graphman.postman_collection.json)

• Added validationStatus and validationStatusDescription fields to existing key queries:
  • keys
  • keyByAlias
• Added validationStatus and validationStatusDescription fields to existing trusted certificate queries:
  • trustedCerts
  • trustedCertsByDn
  • trustedCertByThumbprint
• Added a new Runtime Validation Status folder with 6 query variants:
  • All runtime validation statuses
  • Filter by status (CertValidationStatus)
  • Filter by certificate type (RvsCertificateType)
  • Filter by certificate GOID
  • Filter by expiry within N days
  • Combined filter by status + certificate type

GraphQL Schema (schema/v11.2.2/schema.graphql)

• Created new schema/v11.2.2/ directory using schema/v11.2.1/ as the baseline (v11.2.1 is left untouched — this feature is not available in that release)
• Added to type Key:
  • validationStatus: CertValidationStatus
  • validationStatusDescription: String
• Added to type Certificate:
  • validationStatus: CertValidationStatus
  • validationStatusDescription: String
• Added new query:

  runtimeValidationStatuses(
      status: CertValidationStatus
      certificateType: RvsCertificateType
      certificateGoid: ID
      expiresWithinDays: Int
  ): [CertificateValidationResult!]!

Added new enums: CertValidationStatus, RvsCertificateType, RvsValidationSource
Added new type: CertificateValidationResult
Notes
Schema changes are scoped to v11.2.2 only; v11.2.1 and earlier are unchanged
The runtimeValidationStatuses query is read-only — no mutation changes required

[gh683626]

Cursor-opus:

GraphQL schema file (schema/v11.2.1/schema.graphql) not updated

The graphman-client repo maintains versioned GraphQL schema files. The current schema/v11.2.1/schema.graphql in main has no runtimeValidationStatuses query, no CertValidationStatus enum, no RvsCertificateType enum, no RvsValidationSource enum, and no CertificateValidationResult type. The Key type and Certificate type also don't include the new validationStatus / validationStatusDescription inline fields.

This is the biggest gap. The schema file is the canonical reference for developers integrating with Graphman. Without updating it, consumers won't discover the new API.

[DamandeepToor]

@gh683626 , Ask Cursor to compare this PR with 11.2.2 (latest - urumi Branch ) as 11.2.1 does not have this change??

[gh683626]

@gh683626 , Ask Cursor to compare this PR with 11.2.2 (latest - urumi Branch ) as 11.2.1 does not have this change??

Cursor-opus: The right approach is:

1. Create a new schema/v11.2.2/ folder — following the existing versioning pattern
2. Copy the 11.2.1 schema as the baseline — since 11.2.2 builds on 11.2.1
3. Add the cert validation status changes to the 11.2.2 copy — the new enums, types, query, and inline fields
4. Leave schema/v11.2.1/schema.graphql untouched — it should remain as-is since the feature doesn't exist in that release