fix(types): avoid adding non-existent properties from model constructor for typegoose

[vkarpov15]

Fix #11960

Please take a look @mohammad0-0ahmad

Summary

In #11563, it looks like the model constructor pulls types from the parameter to the model constructor, which is very wrong. @hasezoey reported that this also causes issues for Typegoose.

The tests in document.test.ts#L195-L196 are also wrong, unExistProperty shouldn't be defined on the document instance. See the below script:

const mongoose = require('mongoose');

void async function main() {
  await mongoose.connect('mongodb://localhost:27017');

  const Test = mongoose.model('Test', mongoose.Schema({ name: String }));
  const doc = new Test({ name: 'test', unExistProperty: 1 });
  console.log(doc);
  console.log(doc.name); // 'test'
  console.log(doc.unExistProperty); // undefined

  await mongoose.disconnect();
}();

Examples

[mohammad0-0ahmad]

Hello @vkarpov15!
The changes look good to cover the regression.
Because of the requirements, you described "arbitrary objects in new and create and insert". I did these changes.
Anyway, I would like to say this changes make it better, and I would prefer as will to prevent adding "arbitrary objects" when strict mode is enabled.
I will consider making that available, "If you think that correct"
Thanks for fixing this regression @vkarpov15, and sorry for the trouble @hasezoey, and thanks for reporting the issue.
Best Regards!