transformInteriorValue doesn't handle conversion properly

New Issue Checklist

• Report security issues confidentially.
• Any contribution is under this license.
• Before posting search existing issues.

Issue Description

Since transformInteriorValue https://github.com/parse-community/parse-server/commit/4d4361451cdefa2592b92e8fd54c459b03190205, the code never trigger the logics after value !== CannotTransform. This bug was noticed and fixed in #8209 in a wrong way, and later #8446 introduced a (partially) corrected but duplicated fix.

Steps to reproduce

Actual Outcome

Expected Outcome

Environment

Server

• Parse Server version: 7.4.0
• Operating system: Ubuntu
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): AWS

Database

• System (MongoDB or Postgres): MongoDB
• Database version: 5.0.18
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): AWS

Client

• SDK (iOS, Android, JavaScript, PHP, Unity, etc): JavaScript
• SDK version: 5.3.0

Logs

Start by tracing transformInteriorValue and compare its current behavior with the fixes discussed in issues #8209 and #8446 and commit 4d4361451cdefa2592b92e8fd54c459b03190205. Done means the conversion logic after value !== CannotTransform is reached correctly without retaining duplicated or incorrect fixes.