Fix: Prevent crash in Document.prototype.init() with null/undefined

[Vegapunk-debug]

Fix: Prevent crash in Document.prototype.init() when called with null/undefined

Summary

Calling Document.prototype.init() with null or undefined currently throws a low-level
TypeError (Cannot read properties of null (reading '_id')). This PR adds an explicit
null/undefined check and throws a proper ObjectParameterError instead.

Motivation and Context

init() is part of the public API. While normally used internally, custom scripts or plugins
may pass invalid input. The new error message improves developer experience and prevents an
unexpected crash.

Reproduction

const mongoose = require('mongoose');
const doc = new mongoose.Document({}, new mongoose.Schema({ name: String }));

// Before:
// TypeError: Cannot read properties of null (reading '_id')
// doc.init(null);

// After:
// ObjectParameterError: Parameter "doc" to init() must be an object.
doc.init(null);

Testing

• I have verified locally using the reproduction script above.
• Also, ran npm test to ensure no regressions.

Kindly please review the pull request and merge it.

Thank you!

[Vegapunk-debug]

@vkarpov15, Kindly please review the pull request.

[vkarpov15]

Please undo unrelated formatting changes, this PR is impossible to review

[Vegapunk-debug]

@vkarpov15 Thanks for the feedback!. I've reverted the unrelated formatting changes and updated the PR to include only the fix and a regression test. Ready for review.

[Vegapunk-debug]

Hello @vkarpov15, I have made all the necessary changes. Please take a moment to review them.
Thank you !

[vkarpov15]

Please undo all the unrelated formatting changes