Misleading API docs for /api/v1/projects/{slug}/upload

[TheSuperGamer20578]

Observed/problematic behavior

The documentation for /api/v1/projects/{slug}/upload fails to mark several fields as required in the versionUpload part and there is no error handling for this with the API responding with a status code of 500 with a generic message as opposed to the correct status of 400 with an appropriate message.

Expected behavior

The documentation should mark all required fields as required, and the API should return an appropriate status code and error message if any required fields are missing or invalid.

Steps to reproduce

1. Send a request to /api/v1/projects/{slug}/upload with the minimum required payload stipulated by the documentation
2. Observe a status code of 500

Other

No response