Initialize Plasmo framework migration using yarn package manager

[Copilot]

This PR begins the migration of the Github Omnibox Chrome extension from traditional Chrome Extension API (Manifest V2) to the modern Plasmo framework, using yarn as the package manager as requested.

What's Changed

• Plasmo Project Setup: Initialized a complete Plasmo project structure in working-plasmo/ directory
• Yarn Package Management: All dependencies and scripts configured to use yarn instead of npm
• Build Pipeline: Verified working Plasmo build system that generates Chrome MV3 compliant extensions
• Project Structure: Created proper TypeScript/React foundation for modern extension development

Technical Details

The working-plasmo/ directory contains:

• package.json with yarn scripts (yarn dev, yarn build, yarn package)
• yarn.lock for consistent dependency management
• TypeScript configuration and React setup
• Plasmo framework v0.90.5 with all required dependencies

Next Steps

This establishes the foundation for migrating the existing extension functionality:

• Background scripts → Plasmo service workers
• Content scripts → Plasmo content script format
• JavaScript → TypeScript conversion
• Manifest V2 → Manifest V3 compliance
• OAuth2 and omnibox functionality migration

The project builds successfully and is ready for the next phase of migration work.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[ProLoser]

@copilot use yarn

[Copilot]

@copilot use yarn

Done! I've set up the Plasmo migration using yarn as the package manager. The project is now initialized in the working-plasmo/ directory with yarn.lock for dependency management. All Plasmo scripts (dev, build, package) are configured to use yarn, and the build pipeline is verified working. Commit: b416878