BUG-145 - Suite Bootstrap Flow Misses LAN, Credential, Category, And Arr Sync Polish¶

Summary¶

The suite bootstrap and first-run registration flow has several operator-visible regressions:

LAN control-service binds still show an extra warning/confirmation even though the installer already asks for bind addresses.
The bootstrapper can override the child installer root with the default suite path when the caller did not explicitly request that path.
Generated API keys and suite passwords need to be 24 alphanumeric characters.
The credentials HTML page should open service links in a new browser tab.
Full-suite install work does not show enough progress while downloading and extracting Node and Arr dependencies.
aMuTorrent can show only the default eMuleBB category because the eMuleBB manager publishes the default path but does not import non-default categories into the unified category manager.
Prowlarr application indexer sync can run before every Arr application is saved, leaving indexers missing from one or more Arr apps.

[x] LAN service binds do not produce a second non-loopback confirmation or warning once the user picked them.
[x] Bootstrapper forwards InstallRoot to the child installer only when it was explicitly supplied.
[x] New suite password and API keys are 24 alphanumeric characters, and valid 24-character API keys are preserved.
[x] Credentials page service links use a new tab/window with noopener.
[x] Full-suite dependency installation reports download, verify, and extract progress for aMuTorrent, Node, and Arr tools.
[x] eMuleBB non-default categories are imported into aMuTorrent category state on connect.
[x] Prowlarr application sync runs after both Radarr and Sonarr registrations.

npm test -- --test-name-pattern "eMuleBB manager publishes default category path" passed 62 Node tests.
python -m pytest tests/test_suite_installer.py -q passed 29 installer tests.
python -m emule_workspace validate passed after implementation.