Update docs links using the key for searching and not replacing the content

[bethanyaconnor]

Continuation of #45927.

Three things changed from that script:

1. looking for blocks on key instead of name got most of these files
2. As Tim pointed out, the query.count == 1 condition was too constrictive so I wrote a little heuristic to link to the doc in the same programming environment. Any ambiguous ones I added to the list of docs to do a pass on.
3. Don't replace the string with the name, instead keep the text that is already there and add the extra markdown syntax around it

Links

Testing story

Deployment strategy

Follow-up work

Privacy

Security

Caching

PR Checklist:

• Tests provide adequate coverage
• Privacy and Security impacts have been assessed
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked

[tess323]

This looks great - thank you