Only start BLE for workflow when desired

[tannewt]

The previous implementation would always start BLE and rely on advertising logic to make the workflow not available when on USB.

This change removes the "always enable" call in favor of a default value that is on if 1) we determine we should be discoverable or 2) we're already bonded over BLE.

[tannewt]

@bill88t This should improve the RAM impact of BLE workflow. It won't match 9.0.x though because of the BLE related code in IRAM.

[bill88t]

I have good news and bad news.

Good news first, from a quick test, this seems to bring back the ram usage back to normal.

It won't match 9.0.x though because of the BLE related code in IRAM.

I entered an optimization frenzy and now I'm at a net-negative ram usage.

Bad news, brings back #9291.. somewhat.

It no longer produces a crash.
The IO clock or whatever it's called is just slowing down instead of the system clock.
This means, the neopixel goes white (wrong frequency), but the system keeps on running.
The display curiously keeps on going fine (data updating).

[dhalbert]

This makes sense to me.