fix(s136): the boot refusal cases carry an egress allow-list, now that slice 135 asks for one

Merged with slice 135, every regulated case in boot_refusal_node_test stopped at 135's egress refusal (network: :allow with no TRINITY_REGULATED_EGRESS) before the web-auth check it names. The base environment carries the list, as 135 did for regulated_boot_node_test.

Signed-off-by: Ayla Croft <aylacroft@proton.me>

Author: HackTuah

test/trinity_web/auth/boot_refusal_node_test.exs

@@ -100,6 +100,9 @@ defmodule TrinityWeb.Auth.BootRefusalNodeTest do
       {"TRINITY_PROFILE", "regulated"},
       {"TRINITY_AUTHORITY", "WebBootFixture"},
       {"TRINITY_REGULATED_LLM_ENDPOINTS", "https://models.internal"},
+      # Slice 135: a regulated node with the default `network: :allow` needs an egress allow-list,
+      # so every case here has one and refuses (or boots) for the web reason it names.
+      {"TRINITY_REGULATED_EGRESS", "docs.internal"},
       {"TRINITY_MCP_AUTH_PROFILE", nil},
       {"TRINITY_WEB_AUTH", nil},
       {"TRINITY_TRUSTED_PROXY", nil}