ci: deploy to new static component onionservices.tpo

This is the last item needed to fix tpo/tpa/team#41687 (closed)

It will deploy the build directly to production at https://onionservices.torproject.org

In this instance I don't think it makes sense to have a staging URL but if you feel differently let me know and I'll implement the necessary configurations.

Once this is in place I'll deploy a redirection at https://community.torproject.org/onion-services/ecosystem to the new URL.

.gitlab-ci.yml

 ---
 variables:
+  SITE_URL: onionservices.torproject.org
   GIT_SUBMODULE_STRATEGY: recursive
 
 include:
   - project: tpo/tpa/ci-templates
     file:
-      - scripts/apt.yml
-      - pages-deploy.yml
+      - static-shim-deploy.yml
 
   - project: tpo/web/onion-mkdocs
     file:
@@ -23,21 +23,8 @@ build:
     paths:
       - public
 
-pages:
-  rules:
-    # canonical project: deploy to pages for main branch only
-    - if: '$CI_PROJECT_ROOT_NAMESPACE == "tpo" && $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH'
+.pages-deploy-rules:
+  # canonical project: deploy to pages for main branch only
+  - if: '$CI_PROJECT_ROOT_NAMESPACE == "tpo" && $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH'
     # forks: if merge request, deploy to pages on all branches
-    - if: '$CI_PROJECT_ROOT_NAMESPACE != "tpo" && $CI_PIPELINE_SOURCE == "merge_request"'
-
-# trigger a pipeline in tpo/web/community
-# to integrate and deploy latest builds
-trigger-community-build:
-  stage: deploy
-  needs:
-    - build
-  trigger:
-    project: tpo/web/community
-    branch: main
-  rules:
-    - if: '$CI_PROJECT_ROOT_NAMESPACE == "tpo" && $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH'
+  - if: '$CI_PROJECT_ROOT_NAMESPACE != "tpo" && $CI_PIPELINE_SOURCE == "merge_request"'