Migrate FactoryTest_wMenu to PlatformIO

[Yukti007]

Links

• Closes Firmware, Factorytest_wMenu Migrate to PlatformIO #352

What & Why

• Move FactoryTest_wMenu.ino into a FactoryTest_wMenu/ subdirectory (mirrors GPAD_API layout)
• Add platformio.ini targeting ESP32 with all library dependencies explicitly defined: LiquidCrystal_I2C, DFRobotDFPlayerMini, esp32async/AsyncTCP, esp32async/ESPAsyncWebServer, ElegantOTA, OneButton
• Add .gitignore to exclude PlatformIO build artifacts (.pio/)
• Bump firmware version to v0.4.6.0 and update revision history

Note on AsyncTCP / ESPAsyncWebServer library owners:
The lib_deps uses esp32async/AsyncTCP and esp32async/ESPAsyncWebServer rather than the older mathieucarbou/ variants.
ElegantOTA 3.1.7 declares esp32async/ESPAsyncWebServer@^3.7.3 as its own dependency in library.json, which in turn pulls esp32async/AsyncTCP@^3.4.10.
Listing the mathieucarbou/ packages alongside would cause PlatformIO to install duplicate libraries and produce build errors, since PlatformIO treats different owner names as distinct packages even when the code is identical.

Validation / How to Verify

1. Open Firmware/factoryTest/FactoryTest_wMenu/ in VS Code with the PlatformIO extension installed
2. Run PlatformIO: Build — should resolve all libraries and compile without errors
3. Flash to an ESP32-WROOM-32D board and confirm the factory test menu appears in Serial Monitor at 115200 baud

Artifacts (attach if relevant)

• Screenshots / PDFs / STLs
• Logs

Checklist

• Only related changes : FactoryTest_wMenu.ino
• Folder structure respected, work directory : krake\Firmware\factoryTest\FactoryTest_wMenu\FactoryTest_wMenu
• Validation steps written

[Yukti007]

cherry picked changes from Pull request #434 to avoid conflicts