docs: improve README with table of contents (TOC)

[Yogender-verma]

PR Description

Added a Table of Contents section near the top of the README (after the title/intro). The TOC should include links to all major sections using proper Markdown anchor links, and it should be easy to update whenever new sections are added.

Type of Change

• Bug fix (change which fixes an issue)
• New feature (change which adds functionality)
• Documentation update

Select your work-area

• Frontend
• Backend
• Documentation
• Others

Fixes (mention the issue number which this fixes)

#closes #1226

Checklist

• I have updated my branch and synced it with the project's 'develop' branch before making this PR.
• I have optimized the file changes.
• I have added a snapshot of my work example.
• I have made a PR to the project's develop branch.

Undertaking

• My code follows the style guidelines of this project.

• I have performed a self-review of my code.

• I have commented my code, particularly in hard-to-understand areas.

• I have made corresponding changes to the documentation.

• I have checked for plagiarism and assure its authenticity.

• I have read and followed the code of conduct for this repository. I understand that violation of this undertaking may have legal consequences.

• I Agree

[github-actions]

Thank you @, for creating the PR and contributing to our UltimateHealth project 💗.
Our team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

[github-actions]

Automated Review Feedback

Provide actionable comments grouped by severity:

Important

The anchor links in the "Table of Contents" section are mostly incorrect and will not navigate to the intended sections. Markdown automatically generates anchors for headings by converting the heading text to lowercase, replacing spaces with hyphens, and stripping most special characters, including emojis.

For example:

• ## 🚀 Latest Releases will typically generate an anchor #latest-releases, not #-latest-releases.
• ## 🛠️ Tech Stack will typically generate #tech-stack, not #%EF%B8%8F-tech-stack.
• ## Our Contributors ❤️ will typically generate #our-contributors, not #our--contributors-%EF%B8%8F.

Please verify the exact anchor links generated by GitHub for each heading. You can find these by inspecting the HTML of the rendered README.md on GitHub and copying the id attribute of the heading tags. Ensure all links correctly point to their respective sections.

Maintainer Note:

Once the initial automated feedback has been addressed, maintainer @SB2318 will review the pull request for final evaluation.