dshot_beeper_enabled default ON leads to false positives during initial smoke test of a new build

Current Behavior

The dshot_beeper feature is ON by default, i.e. after flashing a new firmware.
When building a new drone, the initial smoke test after soldering battery and motors is to check if
all ESCs make the initialize sound and stay silent after that.
Beeping ESCs are an indicator for electrical issues.
INAV requesting dshot_beeper because (naturally) some peripherals are missing, sends the user
onto a wild-goose-chase for a non-existent electical issue.

Steps to Reproduce

1. Build a new Drone until initial smoke test.
2. Test if ESCs beep indicating an electrical issue.
3. Realize all ESCs are beeping because of dshot_beeper feature requesting it.

Expected behavior

The dshot_beeper should not be enabled by default.

Suggested solution(s)

Disable the dshot_beeper feature by default.

Additional context

First INAV build, first 4in1 ESC build, took roughly an hour to locate the cause and verify that no electrical issues were present.
set dshot_beeper_enabled = off
ESCs are silent after that.

---

• FC Board name and vendor: Matek H743 Slim v3
• INAV version string: 9.0.1

[Phil-MC]

It also leads to FAILURE TO ARM.
Reported on FB Forum

Please disable by default.

[sensei-hacker]

I took care of the failure to arm in a previous PR.

I understand beeping may be confusing if you're thinking that ESC problems are the only thing that can cause a beep. On the other hand, I think it is useful to let people know about hardware problems. There would be a significant drawback to disabling it.

Just reporting the issue without any agenda. It caught me off-guard as I was unaware of the feature.

I was testing on a lab power supply, intentionally without any USB connected to prevent ground-loops.

I assume having USB connected prevents this feature.