feat: productionize chrome extension build, packaging, validation, docs, and CI artifact workflows

[rudra-chothe]

Summary

• Fixed Chrome extension packaging reliability by ensuring Manifest V3 output is valid and production-ready.
• Added real extension icon assets (16/48/128) and wired them in public/manifest.json.
• Added release automation scripts for extension production flow:
  • sync:manifest-version
  • validate:extension
  • build:extension
  • package:extension
  • release:extension
• Added script files under scripts/:
  • sync-manifest-version.mjs (syncs manifest version from package.json)
  • validate-extension.mjs (validates dist/manifest.json, icons, new-tab target)
  • package-extension.mjs (creates ZIP in release/)
• Updated CI workflow (.github/workflows/ci.yml) to run extension-aware build/packaging checks.
• Added dedicated release workflow (.github/workflows/release-extension-artifact.yml) that triggers on tags/releases and uploads extension ZIP as CI artifact.
• Updated README.md with full production release instructions and new scripts reference.
• Included lockfile updates from dependency install and minor index.html formatting normalization from tooling.

Closes #121

Type of Change

• Bug fix
• New feature
• Documentation update
• Refactor (no behavior change)
• Chore / tooling
• UI polish

Screenshots / Screen Recording

How to Test

1. Install dependencies:

   npm install

2. Verify lint/typecheck/build:

   npm run lint
   npm run typecheck
   npm run build

3. Run extension production pipeline:

   npm run release:extension

4. Confirm ZIP is created under:
   • release/dinam-extension-v<version>.zip
5. Validate unpacked extension locally:
   • Open chrome://extensions
   • Enable Developer mode
   • Load unpacked from dist/
   • Open a new tab and verify Dinam loads
6. (Workflow validation) Trigger new workflow:
   • Push a tag like v0.0.2 or use workflow_dispatch
   • Open Actions → Extension Release Artifact
   • Confirm artifact upload contains extension ZIP

Checklist

• I linked the related issue, if one exists.
• I assigned myself before opening the PR, if required.
• npm run lint passes.
• npm run typecheck passes.
• npm run build succeeds.
• I reviewed my own changes before requesting review.
• I did not change unrelated files.
• I updated documentation if needed.

[AshutoshDash1999]

@rudra-chothe please fix the merge conflict

[rudra-chothe]

@rudra-chothe please fix the merge conflict

solved merge conflicts

[rudra-chothe]

Thanks for merging, just want to know how this contribution will reflect to the GSSoC 26 portal