combine code/.gitignore and the one at the root of the repo

.bandit was part of codacy checks suite, current python code
should probably be updated to use either pylint directly and (/ or)
through the codeql python workflow

Since 'Enter' is also a submit button and another style gets applied,
both seem to overlap. Not very important on a desktop, but might be
easier to navigate on mobile screen
(plus, move settings backup buttons back at the top, accidentally moved
those to the bottom in the previous commit)

On the DEBUG page as well, trying to fix the scrolling behaviour when the
logging stream just started and will only jump after it spends some time at
the top row. Watching the element state to pause the autoscroll when we
manually move the slider, and resume it once the slider touches the bottom
of the textarea. Entering the command will reset the state and enable
the autoscrolling immediately

Separate variables that are used just for the internal loop,
and the ones that are supposed to go into the client as args

Clean up logging and the terminal output, certain things are
now visible through the settings query and there's no need to
dump the build value

Resolve the issue with the UnixHostDuino not really being compatible
with the esp8266 Core String (...and the rest of the Core, as well)

Port the CMakeLists.txt from the rpnlib and update it use FetchContent
instead of either manually fetching dependencies or using PIO artifacts
Caching is *expected* to work, but might need slight adjustments

Make more use of control-groups instead of adding a manual alignment
class to each element. Surprisingly, this is slightly larger than the
previous .gz.html output, but not enough to not consider the readability.

Status page updated to take the lengthy hostnames and version strings
into an account, remove those from the sidebar.

Clean-up terminal module. Use the same style for both input and output,
move the terminal handler and debug handler into an appropriate .cpp

Generate explicit events. Don't have a separate group observer that
tracks deletion, but handle it immediately from the 'button' event

Replace kv array with a direct key updates. While the backed part still
must optimize for size, from this side we should operate on keys directly

Using a more 'specific' CSS rule to override it's width and height

In case the measurement is unitless, make sure to substitute the empty
.units[id] value with an empty string instead of the ambigious 'undefined'

Settling on naming 'options' for enumerations (...possibly, everything
else in the future, would that make sense to store for 'setting' object)

Update terminal commands that were reporting status to also report a
full list of 'indexed' settings for the specific entity
Also updates the WebUI outputs which are (hopefuly) are already handled
as-is through the .js processing pipeline and the .html properties
receiving certain special string values

More namespacing and save ~2KiB of RAM by reducing the amount of loaded keys strings
However, ROM side of things may suffer b/c of template specializations for the
generic conversion functions when there are many different types involved.

Since we know the key-defaults ahead of time, move those there as well
Also tweak alignment of the resulting structs to be % 4

Renamings, and fix duplicate code paths and actually use all of relays
for the status check instead of just one (like the FOLLOW does)

And since WebUI payload used it, this was not reported as 'unused'

Make sure we seamlessly handle 'convert' for the number and the string version.
And since it is a two-way map, update 'serialize' to use it as well instead of
either a simple static_cast<int> or duplicating the same strings used in 'convert'

Only string literals or static vars can be used in constexpr context,
but those can still be shoved into the flash region via PROGMEM.
Notably, PSTR(...) inside of a lambda is not a constexpr.

Some quirks to work out
- we don't 'enumerate' things through compiler, enum values may go
  missing since it is not a switch-case
- 'get' default value via query still requires us to know the settings
  key in the first place. and it still needs an explicit call to
  'serialize'
- sensor units are stringified as their display value.
  but, this also avoids two different 'string' versions of those
- EnumOptions struct instance may also be in PROGMEM, but one needs
  to be very careful to only allow aligned access to it's members
  (which currently means we can't use 8bit or 16bit 'enum class'es)

If the endpoint receives no header, treat it as '*/*'

Don't fail prematurely, since asyncwebserver handler needs to claim the
request to issue a custom response code.
ref.
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/406
- https://datatracker.ietf.org/doc/html/rfc7231#section-6.5.6

cstring's *cmp* return result is integer, not boolean
Pulse processing should only trigger when *current* state is not normal

Remove the ticker dependency, and make sure 'save' callback does not
override itself when at least one relay does not set the 'persist' flag

Also fixing accidental copies of the timer object.