feat(model): allow passing timestamps option to Model.bulkSave(...)

[AbdelrahmanHafez]

fixes #12059
I also refactored bulkSave to use async/await instead of the ugly promise chain, even though I wrote it, I find it difficult to read.
This comes with the downside of shorter stack traces, hopefully, this is not an issue.

@vkarpov15
There is a test failing, bulkSave calls bulkWrite with timestamps false, so mongoose sends the writeOperations to MongoDB without updatedAt or createdAt, but the documents in memory still have updatedAt and createdAt that is inconsistent with the database.

This happens when we document.schema.s.hooks.execPre('save',...). Do you know if there is a way to make pre-save hook not update timestamps? or pass an option to it? pre-post hooks seem like a blackbox to me and for years I couldn't figure out how they work.

[vkarpov15]

@AbdelrahmanHafez I think the issue is this line:

mongoose/lib/helpers/timestamps/setupTimestamps.js

Lines 42 to 45 in c48461a

	const timestampOption = get(this, '$__.saveOptions.timestamps');
	if (timestampOption === false) {
	return next();
	}

. setupTimestamps() registers a pre('save') hook that sets timestamps unless this.$__.saveOptions.timestamps === false.

I think that bulkSave() needs to set doc.$__.saveOptions = options on every doc being saved.

[AbdelrahmanHafez]

Thanks, @vkarpov15, that fixes it. t👍

[vkarpov15]

Nice, thanks 👍