Allow to exclude fields updatedAt, createdAt

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

The main purpose of excluding fields when fetching a Parse.Object is to avoid unnecessary data traffic, which can be a significant cost factor.

Even when excluding all fields with select([]), the following fields are always fetched: ['objectId', 'createdAt', 'updatedAt', 'ACL']. While the keys objectId, ACL may be technically required by Parse Server and SDKs to handle the object, the fields createdAt, updatedAt do seem less relevant and should be excludable.

Feature / Enhancement Description

Allow to exclude the fields createdAt, updatedAt.

Example Use Case

(none)

Alternatives / Workarounds

Use a MongoDB aggregate call to return a raw JSON, which has several disadvantages on the database and server side.

3rd Party References

(none)

Start by tracing Parse.Object fetches using select([]), then inspect the query and serialization paths that preserve objectId, createdAt, updatedAt, and ACL. Check existing Parse Server query tests for field selection behavior. Done means createdAt and updatedAt can be excluded without breaking required object handling or existing fetch behavior.