upgrade dependencies

[wzxxing]

Summary

Changes

Please provide a summary of what's being changed

We need this commit in the proxy to support some advanced features such as passing client info.

Removed checkov because seems that it is not used in the project and causing conflict with this new fastmcp version.

  × No solution found when resolving dependencies for split (markers: python_full_version >= '3.14'):
  ╰─▶ Because your project depends on fastmcp>=2.13.0.2 and fastmcp==2.13.0.2 depends on py-key-value-aio[memory]>=0.2.8, we can conclude that mcp-proxy-for-aws[dev] depends on py-key-value-aio[memory]>=0.2.8.
      And because only py-key-value-aio[memory]<=0.2.8 is available, we can conclude that mcp-proxy-for-aws[dev] depends on py-key-value-aio[memory]==0.2.8.
      And because py-key-value-aio[memory]==0.2.8 depends on cachetools>=6.0.0 and checkov>=3.2.402 depends on cachetools>=5.2.0,<6.0.0, we can conclude that checkov>=3.2.402 and mcp-proxy-for-aws[dev] are
      incompatible.
      And because only the following versions of checkov are available:
          checkov<=3.2.402
          .....
          checkov==3.2.490
      and mcp-proxy-for-aws:dev depends on checkov>=3.2.402, we can conclude that mcp-proxy-for-aws:dev and mcp-proxy-for-aws[dev] are incompatible.
      And because your project requires mcp-proxy-for-aws[dev] and mcp-proxy-for-aws:dev, we can conclude that your project's requirements are unsatisfiable.

User experience

Please share what the user experience looks like before and after this change

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• I have reviewed the contributing guidelines
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented

Is this a breaking change? (Y/N)

• Yes
• No

Please add details about how this change was tested.

• Did integration tests succeed?
• If the feature is a new use case, is it necessary to add a new integration test case?

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.