Saving cloned object returns same objectId

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest version of Parse Server.

Issue Description

Saving a cloned object which had authData set, returns new object with same objectId for _User class.
Issue originally discovered in https://github.com/parse-community/parse-dashboard/pull/1697.

Steps to reproduce

1. Clone a User object with authData set
2. save that object using Parse.Object.saveAll
3. or try this code

let q = new Parse.Query('_User');
q.equalTo('objectId', 'EiWF4cUw9P'); // any User objectId which has authData set
const res = await q.find({ useMasterKey: true });
let toClone=[];
for (const object of res) {
  toClone.push(object.clone());
}
await Parse.Object.saveAll(toClone, { useMasterKey: true });

Actual Outcome

returns object with same objectId & other fields as well.

Expected Outcome

should have new objectId & unique username

Failing Test Case / Pull Request

• 🧐 I submitted a PR with a failing test case.
• 🤩 I submitted a PR with a fix and a test case.

Environment

Server

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

Database

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

Client

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

Logs

Start with the Parse.Query and Parse.Object.saveAll flow shown in the reproduction, focusing on cloning _User objects that contain authData and the MongoDB persistence path. Reproduce with Parse Server 4.5.0 and MongoDB 4.4. Done means the cloned user receives a new objectId and unique username, with a regression test covering saveAll.