[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

サービスレコードを書き込む API デプロイフローを追跡することから始め、services コレクションと environments コレクションへの更新を比較します。同じアプリケーションをまず Dev に、次に Prod にデプロイして問題を再現し、その後、保存されたサービスデータと Dashboard の結果を確認します。両方の環境が表示されたままで、既存の環境を他の環境を削除せずに引き続き更新できれば完了です。

索引モデルが issue の本文から書いたものです。