Bulk update targets with new pwm output assignments

[mmosca]

@sensei-hacker

This pull request updates most (all) targets to use the new TIM_USE_SERVO / TIM_USE_MOTOR for servos and motor, unlocking the benefits of the new timer allocation. Some targets may change the default output allocation and could need manual overrides to match an existing setup, but most seem to behave the same as before, with the default mixes.

AIO are left as TIM_USE_MOTOR, but I may have missed some.

Some targets did not assign motors to the first outputs in fixed wing mode, in those cases I have manually set an override on the expected timer.

Usually this would result in FW working as before, and MC working as before, as long as the number of motors is bigger than the outputs sharing a timer (usually 2).

Users can still change overrides after the fact and get whatever combination they want.

Quite a few targets had different outputs on the same timer with conflicting functions, these should all be fixed now.

[mmosca]

Other targets I have flagged during initial bulk changes

mosca@ham:~/dev/inav/src/main/target$ grep -r 'used to be fw moto' . | cut -d: -f1 | sort | uniq
./CLRACINGF4AIR/target.c
./FIREWORKSV2/target.c
./FOXEERH743/target.c
./GEPRCF722_BT_HD/target.c
./IFLIGHTF7_TWING/target.c
./MAMBAF405_2022A/target.c
./MAMBAH743/target.c
./MATEKF405CAN/target.c
./MATEKF722SE/target.c
./OMNIBUSF7NXT/target.c
./RUSH_BLADE_F7/target.c
./SKYSTARSF722HD/target.c
./SPEEDYBEEF4/target.c
./SPEEDYBEEF7MINI/target.c
./SPEEDYBEEF7V2/target.c
./SPRACINGF4EVO/target.c

[mmosca]

RUSH_BLADE_F7 it favoring the mc configuration instead of fw, since it would end up with m1, m2, s1, s2, m3, m4 instelad of m1-m6