fix(foxess_h3_smart): record hardware verifier

[frahlg]

What

• record the FoxESS hardware verifier and latest test date
• bump foxess_h3_smart from 0.9.2 to 0.9.3
• refresh the manifest, package recipe, index and support status

Why

FTW requires every production driver in its offline recovery bundle to name a verifier and date. FoxESS had reviewed hardware notes but lacked those two metadata fields, so FTW rejected it when added to the bundle.

No register, sign, lease or control logic changes.

Evidence

• make test-driver ID=foxess_h3_smart: 63 passed, 5 skipped
• FTW and Blixt L1 package candidates build
• make check: 3518 passed, 1421 skipped
• existing hardware evidence: four days on one 1K5-HI-10-V1; H3-Smart hardware remains untested

[frahlg]

FTW's recovery-bundle test found the missing verifier and date. This PR now records the existing four-day 1K5-HI-10-V1 evidence, changes no register or control logic, and passes all six required checks plus the local driver, package and full catalog suites. No review threads are open; merging this before the FTW pin update.