Start every worker thread through the executors module

Thirty-nine spawn sites in dr-ui, and one in the Android entry point,
called std::thread::spawn or a Builder of their own, and most of the
threads they started were <unnamed> in a panic message or a profiler.
Each now calls executors::spawn with its executor and a role, so the thread is
named <executor>:<role> — net:sync, decode:thumbs, io:catalog-open —
and knows which executor it is on. The three that already set a name
(automation, import, prefetch) keep their name as the role.

Behaviour is unchanged: each job still gets a thread of its own when it
starts, and spawn panics where std::thread::spawn did.

The module's documentation now says how a job is assigned: by what it
spends its time on, so a sweep that fetches bytes and then decodes them
is Decode, and a sidecar write that touches the catalog is Network.

Left as they were: the segmentation and refine workers in masks_ui.rs,
which another change is reworking, and test-only threads.

ui/dr-ui/src/export.rs

@@ -55,6 +55,7 @@
 //! same file from the grid does — subject, both times, to what the settings
 //! allow (FR-EXP-8).
 
+use crate::executors::{self, Executor};
 use std::collections::HashSet;
 use std::path::{Path, PathBuf};
 use std::rc::Rc;
@@ -414,7 +415,7 @@ pub fn spawn_upload(
 ) -> std::sync::mpsc::Receiver<UploadMessage> {
     let (tx, rx) = std::sync::mpsc::channel();
 
-    std::thread::spawn(move || {
+    executors::spawn(Executor::Network, "upload", move || {
         let rt = match crate::net_runtime::build() {
             Ok(rt) => rt,
             Err(e) => {
@@ -665,7 +666,9 @@ pub enum BatchMessage {
 /// Export a selection on a thread of its own.
 pub fn spawn_batch(request: BatchRequest, cancel: Cancel) -> Receiver<BatchMessage> {
     let (tx, rx) = std::sync::mpsc::channel();
-    std::thread::spawn(move || run(request, &cancel, &tx));
+    executors::spawn(Executor::GpuSubmit, "export", move || {
+        run(request, &cancel, &tx)
+    });
     rx
 }