[Fix] Update mamba_ssm to 2.2.5

[elvischenv]

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• The test plan, such as providing test command.
• The test results, such as pasting the results comparison before and after, or e2e results
• (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.

Purpose

When installing dev requirements via uv pip install -r requirements/dev.txt, mamba-ssm==2.2.4 is failed to install.

  × Failed to build `mamba-ssm==2.2.4`
  ├─▶ The build backend returned an error
  ╰─▶ Call to `setuptools.build_meta.build_wheel` failed (exit status: 1)

Previous WAR for mamba-ssm==2.2.4(#17070, #16859)
Upgrading to mamba-ssm==2.2.5 could root-fix the issue.

Test Plan

Test Result

(Optional) Documentation Update

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[gemini-code-assist]

Code Review

This pull request updates the mamba-ssm dependency from version 2.2.4 to 2.2.5 to fix a build failure. The changes in requirements/test.in and the auto-generated requirements/test.txt are correct. However, I've identified a critical issue where docker/Dockerfile still contains hardcoded references to the old, broken version 2.2.4. This will likely cause the dev and test Docker image builds to fail.

[DarkLight1337]

cc @tdoublep

[elvischenv]

Hi @mgoin, do you think we need this update? Thanks

[DarkLight1337]

Thanks, this change helps simplify our CI/CD