[BLD] Do not trigger deploy on merge to release branches (#4561)

## Description of changes

This removes the `release/**` trigger from the `trigger-deploy` workflow
so that deploys aren't created when hotfixes are merged to release
branches. We want this to be a manual step for the time being to prevent
unintentional deploys of the control plane when we are hotfixing the
data plane.

- Improvements & Bug fixes
- Prevents hotfix merges from triggering a deploy of code that is
potentially behind what is deployed.
- New functionality
  - N/A - removes automation

## Test plan

Manual testing -- we will have to manually deploy changes after merging
hotfixes to release branches.

Author: eculver

.github/workflows/release-chromadb.yml

@@ -220,7 +220,7 @@ jobs:
                 // - This workflow finishes for A and deploys A to Chroma Cloud
                 // Chroma Cloud is now running A, but the last commit was B.
                 "environment": "staging",
-                "planes": "data,control"
+                "planes": "control,data"
               }
             })
 

.github/workflows/trigger-deploy.yaml

@@ -5,8 +5,9 @@ on:
   push:
     branches:
       # main is not included here because it is handled by the release-chromadb.yaml workflow
+      # production deploys (release branches) are also not here because they are currently
+      # meant to be handled manually.
       - rc/**-**-**
-      - release/**-**-**
 
 jobs:
   deploy:
@@ -25,7 +26,7 @@ jobs:
               ref: 'main',
               inputs: {
                 'planes': 'control,data',
-                 environment: '${{ contains(github.ref, 'release/') && 'production' || 'staging' }}',
+                 environment: 'staging',
                 'ignore-lock': true,
                 'oss-ref': '${{ github.ref_name }}',
                 'hosted-ref': '${{ github.ref_name }}'