Failure and error when attempting to nest collection under collection.

### Steps To Reproduce

1. Visit a collection (in my case, [`vault.bitwarden.com/#/organizations/4b78e0d3-7c00-44a0-b0ee-af9501752661/vault?collectionId=2be3982f-947b-49db-8951-af950175a8ac`](https://vault.bitwarden.com/#/organizations/4b78e0d3-7c00-44a0-b0ee-af9501752661/vault?collectionId=2be3982f-947b-49db-8951-af950175a8ac)).

1. Modify that collection:


1. Save:


### Expected Result

It should have nested the collection.

### Actual Result

An error appeared (and, presumably, the collection was not nested):


### Additional Context

I have posted logs to [`gist.github.com/RokeJulianLockhart/6c3e55ebdb315e287262475418124454`](https://gist.github.com/RokeJulianLockhart/6c3e55ebdb315e287262475418124454#file-identifer-sqiikt-txt-markdown).

### Operating System

Linux

### Operating System Version

Probably either:

1. (< whatever version was released into the stable channel before `+2024-01-20T16:31:11+00:00` of) openSUSE Tumbleweed, or:
2. (< V41 of) Fedora's KDE Spin.

### Web Browser

Firefox

### Browser Version

< `firefox-134.0.1-1`

### Build Version

[2023.8.2](https://vault.bitwarden.com/#:~:text=Version-,2023.8.2%20)

### Issue Tracking Info

- [X] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

Start in the web vault using the collection URL and reproduction steps against a current build, then compare the result with the reported 2023.8.2 behavior and the linked logs. Done means modifying a collection to nest it under another collection saves successfully without the reported error.

Written by the indexing model from the issue text.