Download a screen's firmware and put it on from your own computer (0.2.68)

GitHub issue #8: Home Assistant on a server or virtual machine is out of
reach of the screen. New screen and Firmware & USB get a Download choice:
ESP Screens builds the profile's firmware as always and offers ESPHome's
factory image, which the owner flashes with ESPHome Web in Chrome or Edge.

- Firmware: a download job compiles without uploading; only the image of
  the profile's latest successful build in this process is served, a new
  job withdraws it, and a build without a factory image fails.
- USB on the Home Assistant machine stays first in both lists, also before
  a board is plugged in; Download and Later stay chosen once picked.
- The not-yet-in-Home-Assistant card knows a downloaded screen.
- The device name pattern is valid again under Chrome's v flag.
- Docs: README, DOCS, EASY_SETUP, DOCKER, TROUBLESHOOTING. App only;
  firmware stays 0.2.58.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

screen_manager/app/static/style.css

@@ -1335,6 +1335,32 @@ pre {
   overflow-wrap: anywhere;
   font-size: 12px;
 }
+/* Download: the built firmware and how to put it on the screen from your own computer. */
+.download-box {
+  padding: 14px;
+  border: 1px solid var(--line);
+  border-radius: 12px;
+  background: #f7f9fc;
+  margin: 4px 0 16px;
+}
+.download-box a.button {
+  background: var(--accent);
+  color: white;
+  overflow-wrap: anywhere;
+}
+.download-box .steps {
+  margin: 14px 0 6px;
+}
+.download-box .steps li {
+  margin-bottom: 6px;
+}
+.download-box a:not(.button) {
+  color: var(--accent);
+}
+.download-box > small {
+  margin-top: 10px;
+  line-height: 1.45;
+}
 #install-log-wrap {
   margin-top: 12px;
 }