also queue fallback check instead of resolving it in the timer
resolve #2571

early init plus simple state switch w/ api

* dynamic relays should not overlap with configuration
* prefer explicit relay configuration vs. dynamic addition

resolve #2568

fix test case for 0b1... >32chars

allow to schedule pulse timer for the current status by disabling 'toggle' (bool)

- pending changes, fix previous snapshot update
- mention espurna-nightly-builder switch

group changes by tag / snapshot name

amend 542188dd

resolve #2564

resolve #2563

amend b8921b9a89

* customize our multipliers. accuracy is a generic multiplier, mostly
  depends on the environment temperature (see datasheet). sensitivity is
  a ratio between the currently set mtreg value and the default
  e.g. for mtreg 31, sensitivity is .45; for mtreg 69, sensitivity is 1.
* non-blocking pre(); since we have tick(), just wait until the reading
  is available instead of stopping everything else in the sensor loop
* more specific error state when we are not ready to return a value

return half of raw value in both modes involving it
resolve #2550 (just for the sensor, no global setting yet)

ref. #2483, #2546 and #2554
instead of waiting for our time window, attempt to read & parse everything
discard unknown data more frequently, and attempt to store more data as well

resolve #2558
resolve #2559

- revert to ignoring rgb in color+white+cct case by resetting all its
  inputs to minimum and only controlling white channels
- ignore ww and cw in rgb+cct case; use approximated color, thus allowing
  us to set a different 'cold temperature' limit
- fix webui layout rules based on root element class(es) and consistent
  order for our control elements that does not depend on the order in which
  `processData` handles configuration kvs
- internal refactoring to flatten input processing funcs selection
  (to possibly replace our boolean flags with a simple list)

...and since it still causes hwdt crashes

ref. #2547, tell gpio side that we don't need any init

may do weird stuff after runtime pin changes, since we won't know our
new pins due to the order of setup() functions

same as original fix for the Core
fix footer into a single line and add UTC alias notice

make use of our apply() objects for value replacement in-place
also revert the white channel mode change that ignores rgb output factor