feat: Implement Walmart scraper and integrate with existing architecture

- Added Walmart scraper to scrape product data from Walmart.com, including category pages and product details.
- Introduced a stealth browser module to handle bot protection and improve scraping reliability.
- Created a SQLite database for tracking product history, price changes, stock events, and user favorites.
- Developed a Discord bot for user interaction, allowing location setting and stock checking at local stores.
- Implemented a favorites system to manage priority products and categories with custom notification settings.
- Added news aggregation module to fetch and analyze Pokemon TCG news from various sources.
- Created tools for API discovery and monitoring, including a backend monitor for detecting new products.
- Added unit tests for database operations, product filtering, and API endpoints to ensure functionality.
- Enhanced existing modules with improved error handling and logging for better maintainability.

docs/POKEMON_CENTER_DROPS_NOTES.md

@@ -0,0 +1,46 @@
+# Pokemon Center Drop Strategy Notes
+
+Source: https://www.pokepullz.ca/blog/pokemon-center-drops-guide.html
+
+## Queue System
+- Pokemon Center uses a **randomized virtual queue** that activates before major drops
+- Position is NOT based on when you arrived - it's assigned randomly once queue activates
+- This prevents site crashes and distributes access fairly
+
+## Timing Signals
+- Security changes on the Pokemon Center site serve as early warning signals that drops are imminent
+- Products sometimes load in waves rather than all at once
+
+## Multi-Device Strategy
+1. Join queue on primary device (desktop on WiFi) first
+2. Wait a few minutes, then join on second device (phone on mobile data)
+3. This gives you two separate queue positions and accounts for staggered product loading
+
+## Technical Tips
+
+### The Cart Trick
+When Add to Cart button isn't displaying during glitchy drops:
+1. Click the cart icon to go to your cart page
+2. Hit browser back button to return to product page
+3. This forces a page reload that may show the button
+
+## Order Flagging Risks (Avoid These!)
+- Typos in billing/shipping information
+- Mismatched address data
+- VPNs or browser extensions
+- Multiple rapid orders
+- Overloaded carts
+- Queue-checking tools or auto-refreshers
+
+## Pre-Drop Prep Checklist
+- [ ] Log into account days ahead
+- [ ] Have devices ready
+- [ ] Monitor Discord alerts
+- [ ] Disable browser extensions
+- [ ] Turn off VPN
+
+## Implications for Our Monitor
+1. **Don't use VPN/proxies during actual purchases** - only for monitoring
+2. **Queue position is random** - early detection still helps you GET in queue early
+3. **Watch for security changes** - could indicate imminent drop
+4. **Multi-wave loading** - may need multiple checks to catch all products