Define when a channel needs to use aux LEDs as part of its operation,
allowing that channel to block RGB voltage when on if configured.

This prevents a user from 3Cing into an aux channel while in one of
these strobes (candle mode and bike flasher) where they will just get
solid aux as a result, while still allowing aux channels to be used
for strobes where it might make sense (e.g. lightning, tac strobe).

Also added uses_aux to the TS10v1 aux channel which I forgot before.

First off, green was not defined properly and was instead defined the
same as a main channel (leading to the behaviour described in the issue
at ToyKeeper#33 (comment)

Second, fix the actual bug causing aux to not work for blinky modes.
Specifically, set_level needs to be patched so that instead of (or as
well as, doesn't really matter) calling set_level_zero(), it will also
check for if the active channel is an RGB channel and if so them clear
RGB state.

set_level_zero was causing aux-based channels to be set to off at level
0 (i.e. level 1). Also added a clarifying comment.

The 0144 model number is reserved for the successor to the Meteor M44.
This is Hank's first AA light, so it's assigned as 0161:
- 01: Emisar
- 6: product line 6
- 1: model 1

For 3V LEDs on a boost/buck dual fuel driver, this allows
routing power around the boost converter in li-ion mode,
to reduce resistance and increase maximum output.
The AA/NiMH mode is unaffected, and boosts as normal.

…can boot

to prevent corrupt data

This was enabled on more build targets before, but the *_ENABLE_PIN
definition names changed and the eeprom code didn't, so it was not
compiled in for a few months on some lights which probably needed it.
To fix that, it's now enabled by default on everything bigger than
attiny85, since it doesn't really hurt anything if it's enabled when
not needed.

- new ramp
- production style config defaults (simple mode, Hank config)
- candle tuning
- fixed way-too-fast thermal regulation
  (might still be a bit fast, but it's a lot better)

…ter died

(saving progress here so I can work on a different branch)

and not letting the magic smoke out of updi adapters any more (probably)

The alkaline detection might be a little too lenient though; it
could potentially fail to activate limits when the cell is completely
full or stronger than an average alkaline.  One of my test cells
measured at 72 / 75, so if it was just a little stronger it'd pass...
but most alkalines I tried were in the 40 to 60 range and failed easily.

OTOH, if I make it easier to fail, it's likely to trip on normal li-ion
cells, and I don't want that.

So as a future enhancement idea, maybe it should have a smaller sag
threshold for AA and a larger threshold for li-ion.  That would reduce
false negatives for AA, while still preventing false positives for li-ion.

(also, fixed bug where a totally empty li-ion didn't get limited)

(so 0 to 255 now goes from 0.00V to 5.10V)

Fixes issue ToyKeeper#40

Use case 1: Updating a t85 light, where tactical mode is useful but
takes some squeezing, and momentary is less useful

Use case 2: Custom builds for people who don't like/want momentary mode

https://docs.github.com/en/actions/using-workflows/manually-running-a-workflow

Based on [SammysHP's patch](ToyKeeper#18),
but only for lockout mode, not tactical.

Same as PL47G2 but with FET PWM levels safe for 219 emitters.

Same as difference between PL47 and PL47-219.

PL47G2 base allows low mode for aux LEDs, PL47 does not.

MCU space on a few lights