Integration and design questions around new CF2 defconfigs (cf2p, cf2t)

[gemenerik]

#1465 added two new defconfigs: cf2p_defconfig (for upgraded propellers) and cf2t_defconfig (for the thrust upgrade kit).

At the moment, they don’t seem to be fully integrated - they aren’t documented, included in build_targets.json, or part of CI or automated testing.

Beyond that, a few broader questions came up while looking at how these are being used:

• Both defconfigs still set CONFIG_PLATFORM_CF2=y and only differ from the base CF2 by the battery compensation setting.
  That raises the question: is this kind of variation best handled through separate defconfigs, or should it be exposed via Kconfig?
• There’s also some blurring between platform identity and configuration. Even though these are clearly still CF2 in software, treating them as separate defconfigs invites interpretation that they represent distinct platforms.
• More generally, it’s not always clear where a particular setting is configured between Kconfig, defconfigs, and platform defaults, it can take effort to track down what’s actually in effect.

Opening this up for discussion: what’s the intended role of these defconfigs, and how should we approach this kind of variation going forward?