llms.txt: link the parameterized API examples instead of bare endpoints

[portdeveloper]

Why:

Closes #45452

The three API entries in llms.txt's "How to use" section link the bare endpoints, which return HTTP 400 as linked. The working parameterized examples already exist in each entry's description, but agents that follow the href without parsing the description get a 400 instead of content.

What's being changed:

In data/llms-txt/config-default.yml, the hrefs for the Article API, Article Body API, and Search API entries now point at the parameterized example URLs from their own descriptions. Descriptions and curl examples are unchanged, and the other entries (Versions, Languages, Page List) already work bare so they're untouched.

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).
• For content changes, I have completed the self-review checklist.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

This pull request contains code changes, so we will not generate a table of review links.

🤖 This comment is automatically generated.

[subatoi]

@portdeveloper Unfortunately we can't accept anything that isn't content-related as a contribution; I'll forward your PR to the relevant team, but I'm afraid the answer remains the same as before, ie that we won't be taking any action at this time. Apologies that this isn't the answer you were looking for!

[portdeveloper]

totally understood, thanks for forwarding it along! one small note for whichever team it lands with: the change only touches the writer-owned copy in data/llms-txt/config-default.yml (the generator script comment says writers edit these configs directly), no code. but no worries either way, feel free to close!