Respect doesn't resolve complex constraint pattern

[AlbinaBlazhko17]

Describe the bug
AJV validation error when using a discriminator with a schema property that uses allOf + not pattern instead of explicit enum values. The discriminator expects the mapped schema's discriminator property to have const or enum, but the AlternativeInstrument schema uses a more complex constraint pattern.

‼️ Error: Ajv error: discriminator: "properties/method" must have "const" or "enum"

To Reproduce

1. Given the openapi.yaml file with the AlternativeInstrument schema that uses allOf + not:

AlternativeInstrument:
  properties:
    method:
      allOf:
        - $ref: '#/components/schemas/AlternativePaymentMethods'
        - not:
            enum:
              - payment-card
              - paypal
              - ach

2. And the openapi.arazzo.yaml workflow file
3. Run: redocly respect openapi.arazzo.yaml
4. See the error: Ajv error: discriminator: "properties/method" must have "const" or "enum"

Expected behavior
The schema should br validated successfully.

Logs

Workflow name: test-cash-payment
 
  stepId - create-cash-instrument 
  ✗ schema check 
     Ajv error: discriminator: "properties/method" must have "const" or "enum"

OpenAPI description

Redocly version(s)
2.20.4

Node.js version(s)
v24

OS, environment
macOs

Additional context
If we use directly enum without allOf + not pattern everything works as expected.
⚠️ We found, that the issue comes from different $ref resolving between respect and lint commands. Because respect $ref is dereferenced, but lint is not.
Lint registers schemas via addSchema/loadSchemaSync with inlineRefs: false.
Respect receives a fully dereferenced schema (refs already resolved inline).

complex-schema-repro.zip

[tatomyr]

Note: The behaviour should be the same for both lint and respect commands.

[tatomyr]

Related: #1232 (comment). So the behavior might be actually correct.