Digest Authorization header have bigger priority despite it described before another authorization

Describe the bug

Digest Authorization header has higher priority despite being described before another authorization type.
So if this type of Authorization is used, it always overrides the last Authorization header.

To Reproduce

Steps to reproduce the behavior:

1. Given this x-security description:

   x-security:
     - scheme:
         type: http
         scheme: digest
       values:
         username: $inputs.name
         password: secret
     - scheme:
         type: apiKey
         name: Authorization
         in: header
       values:
         value: $inputs.secret

2. When respect executed, digest auth header override API-Key header, although it should have bigger priority

Expected behavior

x-security header resolution should follow top-to-bottom order, with the bottom entry having higher priority.

Start by tracing the respect entry point and the x-security header-resolution logic, then reproduce the supplied configuration to observe the digest and API-key ordering. Verify that entries are resolved top to bottom with the bottom entry taking priority, and add or update the relevant regression test if the existing test structure identifies one.