refactor: Use time.Duration for timeout instead of int.

[iFurySt]

Summary by Sourcery

Refactor HTTP request timeout handling to use time.Duration instead of raw integer seconds.

Enhancements:

• Refactor APIStorageConfig and NewAPIStore to use time.Duration for timeout fields, updating imports and function signatures accordingly
• Use the duration value directly for the HTTP client Timeout instead of multiplying seconds
• Update mcp-gateway YAML configuration to accept duration strings and set a default of "30s" for the API timeout

[sourcery-ai]

Reviewer's Guide

This PR refactors HTTP timeout parameters to use Go’s time.Duration instead of int across configuration, store implementation, and default YAML settings.

File-Level Changes

Change	Details	Files
APIStorageConfig.Timeout now uses time.Duration	Imported the time package Replaced int Timeout field with time.Duration	internal/common/config/storage.go
APIStore timeout handling converted to time.Duration	Changed timeout field type to time.Duration Updated NewAPIStore signature to accept time.Duration Assigned HTTP client Timeout directly using s.timeout	internal/mcp/storage/api.go
Default timeout specified as duration string in YAML config	Updated default timeout value to “30s”	configs/mcp-gateway.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @iFurySt - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

suggestion: Clarify Timeout field comment to specify expected duration format

Specify that timeout expects a YAML duration string (e.g., "30s") to avoid unit confusion.

Suggested change

	Timeout time.Duration `yaml:"timeout"` // timeout for http request
	Timeout time.Duration `yaml:"timeout"` // timeout for HTTP request (YAML duration string, e.g., "30s")