📝 Simplify README MethodTable introductions

[JFWooten4]

From #2672 (comment)

There are a few (mostly API) pages that introduce MethodTables which contain functions. In introducing these lists of cards, they repeat the exact information and links in the actual table. This is redundant.

[Copilot]

🟢 Ready to approve

The focused documentation cleanup is complete, preserves relevant information, and leaves all referenced links valid.

This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.

Pull request overview

Simplifies four MethodTable introductions by removing links duplicated in their tables.

Changes:

• Removes redundant inline links.
• Preserves the unique Result Codes caveat after its table.
• Keeps all table links valid and relative.

File summaries

File	Description
docs/platforms/anchor-platform/api-reference/platform/README.mdx	Simplifies the API types introduction.
docs/data/apis/horizon/api-reference/errors/result-codes/README.mdx	Simplifies the result-code types introduction.
docs/data/apis/horizon/api-reference/errors/README.mdx	Simplifies the error categories introduction while retaining unique guidance.
docs/data/apis/horizon/api-reference/errors/http-status-codes/README.mdx	Simplifies the status-code types introduction.

Review details

• Files reviewed: 4/4 changed files
• Comments generated: 0
• Review effort level: Balanced

We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.

[ElliotFriend]

this is a nice instinct, but there might be a problem. i don't think the <MethodTable> component (and its children) end up in the markdown that's served to AI agents. if you click the "view as markdown" button on one of those pages, with these changes, the file would end with There are three types of error responses: followed by nothing.

[JFWooten4]

Good catch

That bug is similar to #2624 (comment), and I think it warrants its own issue since these probably need a fix upstream with the embed button. I don't think it blocks this PR, as we should write the Developer Docs for human Developers first. Agents should be able to figure it out from the folder structure in the interim.