Remove unsupported db options from mongo connection

[omairvaiyani]

A new set of Parse Config options were added in v6 to databaseOptions called enableSchemaHooks and schemaCacheTtl. However, these options are not strictly speaking database options, they instead manage Parse's internal behaviour with relation to the database. This means that MongoDB doesn't recognise these options and so, they must not be passed into the MongoDB client constructor.

This was correctly handled in the MongoStorageAdapter where the new, non-mongodb options are deleted - Screenshot 1 before they're used as MongoDB client options.

However, there remains another area where the unsupported options are passed to a MongoDB client. You can see in Screenshot 2 that _mongoOptions is used directly when connecting to the MongoDB client in the GridFSBucketAdapter.
This is where an error is thrown (screenshots 3 and 4) if a Parse Server uses the new enableSchemaHooks or schemaCacheTtl options.

Screenshot 1

Screenshot 2

Screenshot 3

Screenshot 4