fix: test Flux 2 with native FTMS parameters

[cagnulein]

Summary

• Test the Tacx Flux 2 through the generic FTMS bike path.
• Match the native app's FTMS simulation parameters observed in the BTSnoop log: zero wind and 0x28 / 0x33 coefficients.
• Apply the same parameters to incoming Zwift FTMS simulation packets before forwarding them to the trainer.

Evidence

The latest issue log confirms that selecting FTMS Bike = Tacx Flux-2 33326 creates ftmsbike, discovers FTMS service 0x1826, sends command 0x11, and receives repeated 80 11 01 success indications.

Test plan

• git diff --check
• Desktop qmake build
• Test suite executed
• Verify the PR APK on the Tacx Flux 2 and collect a new debug log

The test suite has one unrelated pre-existing failure in ApexBikeWlt8266BmRegressionTest.MatchingDevicesUseZeroX30PacketsForDistanceCounterMetrics.