Add Remote MCP package sourcing use case

[egorpavlikhin]

Why

OctopusDeploy/OctopusDeploy#47139 ("Expose feeds and package versions to the Remote MCP") shipped four new contract tools on the Remote MCP: find_feeds, get_feed, find_package_versions, and get_latest_package_version. An agent can now read how a feed is configured (including the registry or source it points at) and pick a package version a channel's rules will accept.

The Remote MCP use cases page is structured as a catalog of what the server helps teams do, but had no entry for feeds or package versions, so the documentation trailed the implementation.

What changed

• Added a Package sourcing use case to the Remote MCP use cases page, with example prompts covering the two capabilities the PR delivered: reading a feed's configuration/registry, and resolving package versions (including honouring a channel's version rule). The prompts are grounded in the real motivation for the feature — a Renovate user needing to know which registry a feed points at.
• Updated the page description and modDate to match.

The other Remote MCP page (remote/index.md) intentionally does not enumerate individual contract tools ("We'll add more operations to the contract tools over time"), so it needed no change.

Notes

• No backend/product code here; documentation only.
• Wording and structure follow the existing sections on the same page (concise theme heading, short description, "Example prompts:" list).

🤖 Generated with Claude Code

https://claude.ai/code/session_01UwiRZaThjbqCqxXeTwUBq1

---

Generated by Claude Code

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[team-marketing-branch-protections]

Pull request environment is available at https://stoctodocspr3449.z22.web.core.windows.net/.

You can view the ephemeral environment status in Octopus Deploy.

This environment will be automatically deprovisioned when the pull request is closed, or after 7 days of inactivity.