Refactor `assertion` to take a function to construct a error instead of always constructing the error

Versions

System: linux / macos / windows
NodeJS: 0.0.0
Typescript: 0.0.0
Compiler / Transpiler: tsc / ts-node / ts-jest
Typegoose(NPM): 9.3.0
Typegoose(GIT): commithash
mongoose: 0.0.0
mongodb: 0.0.0
nestjs / nestjs-typegoose: 0.0.0 / 0.0.0
grahpql / type-graphql: 0.0.0 / 0.0.0

What is the Problem?

Currently, when calling assertion, the value in the second parameter, which should always be a error, gets constructed even when not "throwing" it, which can lead to weird error if the values are weird (see #638)

Code Example

class Test {
  constructor(...args) {
    console.log("Test triggered", ...args);
  }
}

assertion(true, new Test("hello");

output:

Test triggered hello

Do you know why it happens?

as explained above

See This Stackoverflow Question & Answer which explains it greatly, thought its for Rust, it still kinda applies to this problem at hand

typegoose / typegoose

Refactor `assertion` to take a function to construct a error instead of always constructing the error #641

Versions

What is the Problem?

Code Example

Do you know why it happens?