route degrade bug

Describe the bug
Please provide details of the problem, including the version of Spring Cloud that you
are using.

i wan't degrade to another route when invoke error with specify http code

Sample
If possible, please provide a test case or sample application that reproduces
the problem. This makes it much easier for us to diagnose the problem and to verify that
we have fixed it.

  - id: gpt-4o
      metadata:
        name: gpt-4o
      uri: https://xxx-xxx-2.xxx-api.xxx
      predicates:
        - Path=/gpt-4o/api/v1/**
        - Weight=gpt-4o, 1
      filters:
        - RewritePath=/gpt-4o/api/v1/(?<segment>.*), /deployments/gpt-4o/${segment}
        - RemoveRequestHeader=Authorization
        - AddRequestHeader=Ocp-Apim-Subscription-Key, xxx
        - name: ModifyRequestBody
          args:
            inClass: java.lang.String
            outClass: java.lang.String
            rewriteFunction: com.ximalaya.infra.deepgate.filters.rewrite.RequestTransformer
            contentType: application/json
    - id: gpt-4o-xxx
      metadata:
        name: gpt-4o
        connect-timeout: 60000
      uri: https://xxx.xxx.com
      predicates:
        - Path=/xxx/api/v1/**
      filters:
        - RewritePath=/xxx/api/v1/(?<segment>.*), /test/v1/ai/xxx
        - RemoveRequestHeader=Authorization
        - AddRequestHeader=Authorization, Bearer xxx
        - name: ModifyRequestBody
          args:
            inClass: java.lang.String
            outClass: java.lang.String
            rewriteFunction: com.ximalaya.infra.deepgate.filters.rewrite.RequestTransformer
            contentType: application/json
        - name: CircuitBreaker
          args:
            name: gpt4oCircuitBreaker
            fallbackUri: forward:/gpt-4o
            statusCodes:
              - 401
              - 403
              - 404
              - 408
              - 502
              - 503
              - 504

Use the supplied Spring Cloud Gateway route configuration as the reproduction case, focusing on the CircuitBreaker fallbackUri and listed statusCodes. Trigger one of the specified HTTP errors and verify whether forwarding to /gpt-4o selects the alternate route; completion should demonstrate the expected degradation behavior or clearly isolate the failing condition.