feat: Implement Smart Prompt Version Control and A/B Testing Sandbox (#102)

[prasiddhi-105]

What type of change is this?

• Bug fix
• Feature
• Docs
• Chore

Related issue

Closes #102

Changes made

• Implemented Prompt Versioning Service: Built src/versioningService.js to manage background state transitions, retention windows, and evaluation matrix tracking via Chrome's local storage infrastructure.
• Created History Timeline UI: Added dynamic view adapters in src/historyComponents.jsx to render iterative prompt timelines with inline structural text-diff highlighting.
• Fixed Vite & Esbuild Compilation Pipelines: Expanded the esbuild configuration parameters in vite.config.js to safely resolve nested JSX structures inside both .js and .jsx extensions across project directories.
• Upgraded Git Hook Configs: Trimmed legacy shell initialization paths inside .husky/pre-commit and .husky/commit-msg to ensure seamless compatibility with Husky v10.0.0 architecture.

How to test

1. Run npm run build in the project root directory to confirm the production build completes flawlessly without syntax analyzer blocks.
2. Open Google Chrome and navigate to chrome://extensions/. Enable Developer mode and load the newly generated dist folder via the "Load unpacked" portal.
3. Access the extension popup pane, execute multiple sequential prompt optimization loops, select performance pairs, and verify side-by-side rendering behaviors inside the A/B Testing Sandbox.

Checklist

• Code follows ESLint rules (npm run lint passes)
• Code formatted with Prettier (npm run format)
• No API keys or secrets in code
• README updated if needed
• Tested locally in Chrome extension