fix(checkout): route dot-new-carrier-bundle on success page + worker pipeline

Follow-on to the trucking new-carrier slug fix:
- success page: add dot-new-carrier-bundle to DOT_SLUGS + NEW_CARRIER_SLUGS so
  the order-confirmation 'what to expect' messaging classifies it as trucking.
- pipeline_orchestrator: the trucking onboarding PIPELINE was keyed under the
  bare 'new-carrier-bundle' slug, which is the TELECOM bundle's slug (also a
  collision at the worker layer). Re-keyed to 'dot-new-carrier-bundle' so a
  trucking bundle never runs the telecom pipeline (and vice versa).

scripts/workers/pipeline_orchestrator.py

@@ -45,7 +45,11 @@ DB_URL = os.getenv("DATABASE_URL", "")
 # (e.g. MC authority needs an *active* USDOT; UCR/D&A need an active USDOT).
 # `activation_target` names what must be active at FMCSA: "usdot" | "authority".
 PIPELINES = {
-    "new-carrier-bundle": [
+    # Trucking/DOT new-carrier onboarding pipeline. Keyed by the DOT-specific
+    # slug (dot-new-carrier-bundle); the bare "new-carrier-bundle" slug is the
+    # TELECOM VoIP bundle, handled by NewCarrierBundleHandler -- they must not
+    # share a key here or trucking orders would run the telecom pipeline.
+    "dot-new-carrier-bundle": [
         {"slug": "llc-formation", "name": "LLC Formation", "wait_for": None},
         {"slug": "ein-application", "name": "EIN Application", "wait_for": "llc-formation"},
         {"slug": "dot-registration", "name": "USDOT Registration", "wait_for": "ein-application"},