[Feat] Add timeouts to VLLM Router configuration

[VariableDeclared]

FILL IN THE PR DESCRIPTION HERE

FIX #706

Currently the router configuration for the backend will be created with defaults, for some models and scenarios this means the Gateway is timing out before vLLM responds. This is a quick fix to allow users to create a timeout. Long term a more elegant solution would be appropriate.

• Make sure the code changes pass the pre-commit checks.
• Sign-off your commit by using -s when doing git commit
• Try to classify PRs for easy understanding of the type of changes, such as [Bugfix], [Feat], and [CI].

[gemini-code-assist]

Code Review

This pull request introduces support for configuring timeouts on route rules in the Helm chart, along with corresponding test cases. The reviewer pointed out a potential YAML parsing issue in values.yaml if a user uncomments the example timeout configuration directly, and suggested a safer way to structure the commented-out example.

[gemini-code-assist]

If a user uncomments the # requests: 300s line directly, it will result in invalid YAML because timeouts is already defined as an inline empty map (timeouts: {}) on the previous line.

To prevent YAML parsing errors when users try to uncomment the example, it is better to comment out the entire block as an example and keep the default timeouts: {} separate.

      # timeouts:
      #   requests: 300s
      timeouts: {}