[BUG] Deploying to new environment overwrites existing service environment

**Describe the bug**
When you deploy a service/application to Dev (for example) it will work fine. it will create the new application, and create the environment.

When you attempt to deploy that same service/application to Prod it will work fine, but I believe it is completely overwriting the object in the services collection, so it essentially deletes the Dev environment, and we now only see the Prod environment.

This is only within the scope of the service in the services collection, both environments will exist in the environments collection as expected.

**To Reproduce**
Steps to reproduce the behavior:
1. Deploy to dev.
2. Go to the Dashboard page, observe it is there as expected.
3. Deploy same app to prod.
4. Go back to the Dashboard page, observe Dev is gone, and only Prod is there.

**Expected behavior**
Deploying to an existing Service, should only add a new environment, or update the existing environment. it should not overwrite the entire environments field.

**Screenshots**
none

**System Information (please complete the following information):**
- API

**Additional context**
None

Start by tracing the API deployment flow that writes service records and compare updates to the services and environments collections. Reproduce the issue by deploying the same application to Dev and then Prod, then inspect the stored service data and Dashboard result. Done means both environments remain visible and an existing environment can still be updated without removing the others.

Written by the indexing model from the issue text.