fix(deps): update swaggerversion to v2.1.26

[mend-for-github-com]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
io.swagger.parser.v3:swagger-parser-v3 (source)	2.1.25 -> 2.1.26
io.swagger.parser.v3:swagger-parser (source)	2.1.25 -> 2.1.26
io.swagger.parser.v3:swagger-parser-core (source)	2.1.25 -> 2.1.26

---

Release Notes

swagger-api/swagger-parser (io.swagger.parser.v3:swagger-parser-v3)

v2.1.26: Swagger-parser 2.1.26 released!

• allow non explicit style and explode with 'explicitStyleAndExplode' option (#​2161)
• fix(#​2104): properly process inline refs in composed schemas (#​2123)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

disabled

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.30%. Comparing base (7a6553f) to head (2e502c3).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##               main    #1091   +/-   ##
=========================================
  Coverage     76.30%   76.30%           
  Complexity     1076     1076           
=========================================
  Files           101      101           
  Lines          5276     5276           
  Branches        504      504           
=========================================
  Hits           4026     4026           
  Misses         1001     1001           
  Partials        249      249           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/flow-framework/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/flow-framework/backport-2.x
# Create a new branch
git switch --create backport/backport-1091-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e49812b8635b85bfd270ea4f72a59d5f7aa74f20
# Push it to GitHub
git push --set-upstream origin backport/backport-1091-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/flow-framework/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-1091-to-2.x.