docs: fix remaining broken links for both typescript and python @bhargavyagnik

[bhargavyagnik]

Which issue(s) does this pull-request address?

Solved #543.

Updated links to existing docs.

Now, as per link checker, the missing links are only
Errors in docs/README.md

• [ERROR] file:///typescript/docs/backend.md%23providers-implementations | Cannot find file
• [ERROR] file:///typescript/docs/tools.md%23using-the-mcptool-class | Cannot find file
• [ERROR] file:///python/tools.md%23using-the-customtool-python-functions | Cannot find file
• [ERROR] file:///python/tools.md%23mcp-tool | Cannot find file
• [ERROR] file:///python/docs/agents.md%23creating-your-own-agent | Cannot find file
• [ERROR] file:///python/backend.md%23supported-providers | Cannot find file

But, this is an issue with fragments. The links are working fine with readme, IDE and website. The link-checker has an issue with finding anchor links in the code. So I will mention this in the PR submitted #542

Closes: #543

Description

Checklist

General

• I have read the appropriate contributor guide: Python
  / TypeScript
• I have signed off on my commit: Python instructions / TypeScript instructions
• Commit messages and PR title follow conventional commits
• Appropriate label(s) added to PR: Python for Python changes, TypeScript for TypeScript changes

Code quality checks

• Linting passes: Python poe lint or poe lint --fix / TypeScript yarn lint or yarn lint:fix
• Formatting is applied: Python poe format or poe format --fix / TypeScript: yarn format or yarn format:fix
• Static type checks pass: Python poe type-check

Testing

• Unit tests pass: Python poe test --type unit / TypeScript yarn test:unit
• E2E tests pass: Python poe test --type e2e / TypeScript: yarn test:e2e
• Integration tests pass: Python poe test --type integration
• Tests are included (for bug fixes or new features)

Documentation

• Documentation is updated
• Embedme embeds code examples in docs. To update after edits, run: Python poe docs --type build

[Tomas2D]

Thank you!