fix: set TEST_MODE_API on the container-start step

The previous patch set TEST_MODE_API on the `E2E Test API` step,
which runs *after* docker compose has already started the rocketchat
container — so the env var never reached the Node process.

Move the export to the `Start containers` steps (CE + EE) gated on
`inputs.type == 'api' || inputs.type == 'api-livechat'` so the var
exists in the shell when docker compose substitutes it into the
container's environment from `docker-compose-ci.yml`.

Author: ggazzo

.github/workflows/ci-test-e2e.yml

@@ -175,6 +175,13 @@ jobs:
 
       - name: Start containers for CE
         if: inputs.release == 'ce'
+        env:
+          # API tests intentionally invoke deprecated DDP methods through
+          # /v1/method.call/:method. The deprecation logger throws under
+          # TEST_MODE, so for api/api-livechat runs we set TEST_MODE_API
+          # to suppress the throw (it still logs). Forwarded via
+          # docker-compose-ci.yml -> rocketchat container env.
+          TEST_MODE_API: ${{ (inputs.type == 'api' || inputs.type == 'api-livechat') && 'true' || '' }}
         run: |
           # when we are testing CE, we only need to start the rocketchat container
           DEBUG_LOG_LEVEL=${DEBUG_LOG_LEVEL:-0} docker compose -f docker-compose-ci.yml up -d rocketchat --wait
@@ -185,6 +192,7 @@ jobs:
           ENTERPRISE_LICENSE: ${{ inputs.enterprise-license }}
           TRANSPORTER: ${{ inputs.transporter }}
           COMPOSE_PROFILES: ${{ inputs.type == 'api' && 'api' || '' }}
+          TEST_MODE_API: ${{ (inputs.type == 'api' || inputs.type == 'api-livechat') && 'true' || '' }}
         run: |
           DEBUG_LOG_LEVEL=${DEBUG_LOG_LEVEL:-0} docker compose -f docker-compose-ci.yml up -d --wait