Console: remember Enable Custom Bitmaps, ship the art; bump suite to 4.11.4.5

Settings -> Enable Custom Bitmaps was a static bool with no backing store:
it defaulted to off on every launch, so an operator had to re-tick it each
session and any custom plasma art was silently ignored until they did. New
ConsoleSettings persists machine-level menu toggles as XML in
%ProgramData%\Tesla Console\console.settings, alongside RPDefaults.rpd /
BTDefaults.btd / local.siteconfig. It is loaded once from Main and never
from a static initializer: the differential suite drives PlasmaBitmaps
directly and must keep seeing the original defaults rather than whatever
this machine has saved. A missing file is the first-run case; a corrupt one
is ignored and rewritten by the next toggle, because losing a menu setting
must never stop the console starting.

Custom art is now version-controlled and rolls with the release. New
Console\Plasma Images\ is copied into the package, and the lookup searches
%ProgramData%\Tesla Console\Plasma Images first and the exe-relative folder
second, so a release can never clobber a site's own name bitmaps.
install.bat creates the data-dir folder before the icacls grant so an
unelevated operator can write it. Ships with three 128x32 name bitmaps
(Deadmeat, Muerte, Phrogg); Muerte arrived as "Muerte_128x32-2.bmp", a name
the lookup can never build, so it is renamed to match its pilot.

Two fixes fell out of making the flag sticky. Path.Combine ran on the raw
participant name outside the try block, so with the option on a pilot named
"A:B" threw ArgumentException straight out of egg generation; names that
cannot be a Windows file name now just render procedurally. And the art was
loaded with Image.FromFile, which keeps the bitmap backed by the file and
locked for its whole lifetime — it is copied out through a stream now, so
art can be swapped between missions without restarting the console.

Verified against the built net40 exe: all three shipped bitmaps resolve by
pilot name, ProgramData wins over the shipped copy, a wrong-size file is
ignored, an illegal-character name does not throw, the file is not left
locked, and the settings round-trip and corrupt-file tolerance both hold.
Diff suite 106/106.

Version bumped 4.11.4.4 -> 4.11.4.5 across Console, Launcher, vPOD, the
install/build banners, the diff-suite version assertion and the README's
latest-release pointer.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Console/README.md

@@ -103,9 +103,16 @@ dependency DLLs copied alongside it).
 
 - `RedPlanet\RPConfig.xml`, `RedPlanet\RPStrings.xml` are loaded relative to the
   exe and are copied to the build output automatically.
-- `Plasma Images\*.bmp` (under `%ProgramData%`) is an **optional** override set;
-  when absent the console renders plasma-display text procedurally, so it is not
+- `Plasma Images\*.bmp` is an **optional** override set for the pod plasma name
+  displays, enabled by *Settings → Enable Custom Bitmaps*. The console looks in
+  `%ProgramData%\Tesla Console\Plasma Images` (the machine's own art, wins) and
+  then in `Plasma Images\` next to the exe (the set that ships with the release —
+  see [`Plasma Images/README.md`](Plasma%20Images/README.md) for naming and sizes).
+  When neither has a match the console renders the text procedurally, so no art is
   required to build or run.
+- Machine-level Settings-menu toggles persist in
+  `%ProgramData%\Tesla Console\console.settings` (XML, written on change by
+  `ConsoleSettings`). Deleting it just restores the defaults.
 
 ## Notes