docs: sort case studies table by lockfile type and project name

[kira88-code]

Summary of Changes

Resolved the case studies navigation issue by reordering and grouping the index table rows in website/docs/case-studies/index.md based on the specified lockfile criteria.

• Lockfile Grouping: Sorted rows strictly by lockfile manager type in the requested sequence: npm ➔ pnpm ➔ Yarn.
• Alphabetization: Fully alphabetized all project entries within their respective lockfile categories (A-Z).
• Data Integrity: Left all key findings, markdown links, and descriptions completely unchanged.

Local Verification

• Successfully ran a local development preview server via npm run start inside the website/ directory to visually verify flawless UI rendering.
• Successfully verified production builds by running npm run build within the website/ folder, ensuring the Docusaurus configuration compiles cleanly with zero syntax or markdown errors.

Closes #544

[kira88-code]

Hi @sonukapo0r,

I've updated the case studies index table according to the acceptance criteria. The entries are now strictly grouped by lockfile type (npm, pnpm, then yarn) and alphabetized within each group.

I also verified the changes locally using both the development server and a clean production build (npm run build) inside the website directory to ensure Docusaurus compiles perfectly with no markdown errors.

Let me know if this looks good to go!

[sonukapoor]

Looks good - clean sort with no content changes. One small fix needed before merge: the file is missing a newline at the end (shown as \ No newline at end of file in the diff). Could you add a trailing newline to website/docs/case-studies/index.md?

[kira88-code]

Hi @sonukapoor,

Quick update on this PR:

1. Resolved the latest merge conflict and integrated the new 'CamoFox Browser' case study.
2. Formatted the table strictly according to the repository's tier-sorting criteria (Grouping by npm -> pnpm -> Yarn, and fully alphabetizing entries within each section).
3. Ensured the trailing newline fix is completely intact to clear the linter check.

All CI builds, security scans, and tests are passing cleanly now. Ready for final review!