fix: use 0x31 metrics for Apex WLT8266BM bikes

[cagnulein]

Summary

• Disable the WLT8266BM 0x30 distance-counter parser for the whole family.
• Keep the standard 0x31 cadence/resistance/distance parsing for these Apex bikes.
• Update regression coverage for multiple WLT8266BM variants.

Evidence

Issue #4886 includes two logs from WLT8266BM_07E2:

• During the static phase, 0x30 increments while 0x31 remains ea503100001400000095, indicating zero cadence.
• During cycling, 0x31 byte 4 changes and produces the expected cadence values.
• Treating 0x30 as distance creates movement metrics while the bike is not being pedalled.

The fix intentionally prioritizes correct behavior for the user-provided WLT8266BM bike family over the previous unverified 0x30 interpretation for other variants.

Test plan

• git diff --check
• Replay of the issue Apex Rides auto transmit/start #4886 log: static phase remains at zero with the 0x31 parser.
• Added TestApexBikeParser assertions for multiple WLT8266BM variants.

Fixes #4886