Add automatic configuration capability and other enhancements for Offline Mode

[brentru]

This pull request adds:

• New Feature ✨ - config.json file is now built automatically!
  • Previously, A user would need to manually build a config.json file and then upload it to a board running WipperSnapper's Offline Mode.
  • Now, the config.json file is constructed during runtime and appears on the first run of the Offline Mode firmware.
• New Feature 💾 - Automatic initialization for the microSD card
  • First attempts to initialize based on the config.json file, then falls back and attempts to initialize based on a #define within ws_boards.h file
• New Feature 🔌 - Automatic Detection, Configuration and Initialization for I2C Components
  • I2C components are now automatically detected and added to the config.json file, without manually editing the file.
  • How this works:
    • 1. All components defined within the config.json file are initialized first
    • 2. WS Offline scans the I2C bus to discover new devices
    • 3. If a new device is found, a best-guess attempt is made to detect and initialize an I2C device candidate
    • 3a) If the candidate is successfully initialized, it is appended to the config.json file to allow it to persist between boots.
    • 4. The runtime executes with both the existing components (defined in config.json) and the new, discovered, components.

[github-actions]

Test Results

6 tests  +6   6 ✅ +6   42s ⏱️ +42s
1 suites +1   0 💤 ±0 
1 files   +1   0 ❌ ±0 

Results for commit 375fd39. ± Comparison against base commit 0de3e5c.

♻️ This comment has been updated with latest results.

[brentru]

@tyeth This PR is passing and ready for review and testing.

Note that you do not need to review every i2c driver/drvName, there's a ton and it'd take too much time.

[brentru]

Hardware Tested:
✅ RP2040 Adalogger + SHT31
✅ RP2040 Adalogger + SHT31 + MUX w/BME280
✅ RP2040 Adalogger + RTC + MUX w/BME280
✅ ESP32-S2 Feather + Adalogger FeatherWing + BME280

[tyeth]

There was some funkiness with the checksum messaging when using offline mode. I think maybe it says mismatch and then successfully verified. Maybe worth quickly checking.
I meant to add that checksum to the config tool too.

[tyeth]

the filename and folder suffix looks like a typo

[brentru]

Not sure how - would you prefer a rename?

[brentru]

I think maybe it says mismatch and then successfully verified. Maybe worth quickly checking.

I fixed this sometime on Thursday and didn't see this while testing. I also verified it against the invalid_checksum unit test scenario:

tests/test_offline.py::test_invalid_checksum Wokwi CLI v0.14.3 (7c0fea04eeb6)
Connected to Wokwi Simulation API 1.0.0-20250406-g04cf145b
Starting simulation...
....
[APP] Attempting to configure hardware...
->[Offline Mode - Invalid Checksum Value] Expected text matched: "[SD] Checksum mismatch, file has been modified from its original state!"
[Offline Mode - Invalid Checksum Value] Scenario completed successfully
PASSED