fix: update CSP and security meta tags

[PranavAgarkar07]

Description

1. CSP style-src was missing fonts.googleapis.com, blocking Google Fonts
2. X-Content-Type-Options was set via non-standard meta tag (should be HTTP header)
3. Missing apple-mobile-web-app-capable meta tag for iOS PWA support

Changes

• Added https://fonts.googleapis.com to CSP style-src
• Replaced X-Content-Type-Options meta tag with comment for server-side config
• Added apple-mobile-web-app-capable meta tag for iOS PWA

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Screenshots

N/A — This PR only modifies HTML meta tags and CSP directives in index.html. There are no visible UI changes. The Google Fonts loading fix has no visual diff, and the PWA meta tags are only relevant when the site is added to the iOS home screen.

Related Issue

Closes #1001

[vercel]

@PranavAgarkar07 is attempting to deploy a commit to the CodeBlooded's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Hi @PranavAgarkar07, thanks for contributing to Nyay Setu! 🎉

I have automatically:

• 👤 Assigned this PR to you.
• 🏷️ Applied the gssoc:approved label.

Our workflows will now analyze your changes to classify:

• 📈 PR Difficulty: level:*
• 🧩 PR Type: type:*
• 🌟 PR Quality: quality:*

Tip

Ensure your PR description references the issue it resolves (e.g. Closes #123). This allows the bot to inherit any additional labels from that issue!

Happy coding! 🚀

[PranavAgarkar07]

@viru0909-dev This PR is ready for review — CI passes, all labels applied (including gssoc:approved). Could you take a look and merge when convenient? Thanks!

[viru0909-dev]

Requires Changes. Please address the following issues:

• PR modifies UI components but no screenshot or video is attached in the description.
  Frontend tests failed:\n\n ❯ src/pages/litigant/DocumentGeneratePage.test.jsx (4 tests | 2 failed) 1376ms ⎯⎯⎯⎯⎯⎯⎯ Failed Tests 2 ⎯⎯⎯⎯⎯⎯⎯ FAIL src/pages/litigant/DocumentGeneratePage.test.jsx > DocumentGeneratePage > copies generated content and calls DOCX export actions FAIL src/pages/litigant/DocumentGeneratePage.test.jsx > DocumentGeneratePage > downloads PDF and handles filename and blob flow Test Files 1 failed | 4 passed (5) Tests 2 failed | 14 passed (16)\n

[viru0909-dev]

Review Summary

This PR has been reviewed and requires changes before it can be approved. The issues below must be resolved.

Issues to Resolve

Result	Check	Notes
FAIL	Description	Description is missing: a Type of Change section; a Checklist section with checkboxes.
FAIL	Checklist	No checklist found in the description.
FAIL	UI Screenshot	This PR modifies UI files but no screenshot or video is attached. Add before/after screenshots or a screen recording showing the change.

Passing Checks

Result	Check	Notes
PASS	Title	Title format is acceptable.
PASS	Issue Link	Issue is linked with a closing keyword.
PASS	Merge Conflicts	Conflict status is not yet computed by GitHub — skipping.
PASS	Branch Freshness	Branch was last updated 2.5 days ago.
PASS	CI / Tests	No CI checks are configured or results are not yet available.
PASS	Code Quality	No code quality issues detected in the diff.

---

To proceed: push the required fixes to fix/1001-csp-security-meta-tags and the PR will be re-evaluated on the next review run.