[Docs]: Setup UI still labels Salesforce-provided servers tab as "(Beta)" after GA

### Affected page or file

- Setup → MCP Servers screen, the tab containing Salesforce-provided standard servers (label: "Salesforce Server (Beta)" / Japanese: "Salesforce サーバー (ベータ)")
- This repository's own header/description (still mentions "(Beta)" in places)
- help.salesforce.com search results for `platform.hosted_mcp_servers.htm` (article title still appears as "Salesforce Hosted MCP Servers (Beta)")

### Describe the issue

After Hosted MCP Servers reached GA, the Setup → **MCP Servers** screen still shows the tab containing Salesforce-provided standard servers as **"Salesforce Server (Beta)"** (Japanese locale: **"Salesforce サーバー (ベータ)"**). This is inconsistent with what the README, Wiki, and Developer Docs already say:

- ✅ README body: *"Hosted MCP servers are now generally available (GA)."*
- ✅ Wiki / *Confirming Availability* (updated 2026-04-10): *"At GA, the MCP servers are disabled by default in your org."*
- ✅ developer.salesforce.com/docs/platform/hosted-mcp-servers/: no Beta marker
- ❌ Setup UI tab label: still shows `(Beta)` / `(ベータ)`
- ❌ help.salesforce.com search result title for the help article: still shows `(Beta)`
- ❌ This repo's own header/description: still includes `(Beta)` in some places

This causes real-world confusion when reviewing whether the feature is production-ready. From the perspective of a customer doing an internal adoption review, it is hard to give an unambiguous "yes, this is GA and safe for production" answer when the Setup screen itself still says Beta — even though every authoritative source says otherwise.

**Environment**
- Salesforce org: Enterprise Edition, Japanese locale
- Spring '26 release
- Observed on: 2026-04-30

### Suggested fix

Either:

1. Update the Setup tab label (and the corresponding Japanese localized string) to drop `(Beta)` / `(ベータ)`, and align the repository header and help.salesforce.com article title accordingly.
2. If the `(Beta)` marker is intentional because **some specific standard servers** within the tab are still pre-GA while others are GA, please clarify which servers are GA vs. Beta in the Wiki / Developer Docs. A per-server availability matrix would let customers make adoption decisions at the right granularity, instead of being blocked by the tab-level Beta label.

### Additional context or screenshots

Happy to attach a screenshot of the Setup UI tab label on request — omitting it from the initial post to avoid accidentally including org-identifying information.