Dshot commands causing motors to spin (when BDIR=OFF)

[limonspb]

Describe the bug

The bug has multiple symptoms.
All of them are reproducible at least on F7 (mine FOXEER F722) when bidirectional dshot is OFF.
Git bisect showed that the issue was introduced here:
#11011

Dshot commands (for example changing motor direction from motor direction dialog) cause all motors to spin for a split second.

To Reproduce

1. Take props off
2. Flash RC2/RC3 with full chip erase
3. Apply custom defaults
4. Set motor protocol dshot 150, 300, 600 (leave bidir OFF)
5. Save
6. Plug the battery
7. Open CLI
8. type "dshotprog 0 7", hit enter
9. All motors except motor 1 will spin for a split second

Command "dshotprog 0 7" means
send DSHOT_CMD_SPIN_DIRECTION_1 command to motor 1
Any command from 0 to 49 causes other motors to spin.

Another way to reproduce:

1. Take props off
2. Flash RC2/RC3 with full chip erase
3. Apply custom defaults
4. Set motor protocol dshot 150, 300, 600 (leave bidir OFF)
5. Save
6. Plug the battery
7. Open motor direction dialog
8. Select not wizard, but "individually"
9. Select motor 1
10. Try to change it's direction
11. All motors will spin for a split second

Expected behavior

Motors should not spin. Motor 0 direction should become
DSHOT_CMD_SPIN_DIRECTION_1

Flight controller configuration

# diff

# version
# Betaflight / STM32F7X2 (S7X2) 4.3.0 Feb 13 2022 / 23:36:19 (7b4415f06) MSP API: 1.44
# config: manufacturer_id: FOXE, board_name: FOXEERF722V2, version: baa1d34a, date: 2021-08-16T07:35:36Z

# start the command batch
batch start

board_name FOXEERF722V2
manufacturer_id FOXE

# master
set motor_pwm_protocol = DSHOT150
set pid_process_denom = 2
set gyro_1_align_yaw = 2700

profile 0

rateprofile 0

# end the command batch
batch end

Flight controller

FOXEERF722

Other components

does not matter

How are the different components wired up

does not matter

Add any other context about the problem that you think might be relevant here

Git bisect showed that the issue was introduced here:
#11011

f6190e2f1ab3d6d51c4268b6fe707682e7bf547b is the first bad commit
commit f6190e2f1ab3d6d51c4268b6fe707682e7bf547b
Author: Steve Evans
Date:   Fri Dec 17 11:16:26 2021 +0000
    Use bitbanged DSHOT by default if dshot_bitbang = AUTO unless F4

[haslinghuis]

@limonspb is this still an issue?