Link guidance for choosing an orchestrator

Nobody has claimed this yet.

### Is your feature request related to a problem?

_Part of the Delegator UX Analysis RFP._

The Orchestrators page is a strong explorer surface. The table is dense, scannable, and well-suited to inspecting the network. The problem isn't the table itself; it's that the page assumes prior knowledge it doesn't always provide. Users arriving without context have no linked explanation of how to evaluate orchestrators, what makes a good choice, or how yield relates to other factors like fee cut, reliability, or stake distribution. Existing documentation on orchestrator selection isn't surfaced from the page.

### Describe the solution you'd like

Keep the Orchestrators table as-is. Adding row-level controls would compromise what's currently a clean, scannable surface. Instead, add lightweight scaffolding around the table: a [linked guide to choosing an orchestrator](https://docs.livepeer.org/v2/delegators/delegation/choose-an-orchestrator), and a clear entry point into the dedicated delegation flow. The existing per-row submenu can remain as a shortcut for users who already know what they want. The deeper question of whether the Orchestrators page should split into "explore the network" and "choose to delegate" views is raised but deferred to Delegation flow section..

### Describe alternatives you've considered

_No response_

### Additional context

_No response_

Start at the Orchestrators page entry point and inspect the existing per-row submenu and delegation flow entry point. Add the choosing-an-orchestrator guide link and a clear delegation entry point without changing the table or its row-level controls; done means both links are visible and the existing table remains scannable.

Written by the indexing model from the issue text.