types: Add Expression Typings to Pipeline Stages

[Uzlopak]

To be implemented:

• Arithmetic Expression Operators
• Array Expression Operators
• Boolean Expression Operators
• Comparison Expression Operators
• Conditional Expression Operators
• Custom Aggregation Expression Operators
• Data Size Operators
• Date Expression Operators
• Literal Expression Operator
• Miscellaneous Operators
• Object Expression Operators
• Set Expression Operators
• String Expression Operators
• Text Expression Operator
• Trigonometry Expression Operators
• Type Expression Operators
• Accumulators
• Variable Expression Operators
• Window Operators

[Uzlopak]

I guess if I do every day about 20-30 Expressions than in 4-5 days this big chunk of code is done.

Then we can use them for the PipelineStages and Queries. Should be better than the any typings we have currently.

Also there is I think a typescript feature were you can build attribute names based on strings to do stuff like key.$ where key is a key in an interface. But I think this could result in annoying issues like somebody using older typescript could not use the typings or you have keys after a projection stage were you don't have the typings of.
So probably better to just use string as type and don't make it too intelligent.

Anyway, I guess, the best benefit will be when the pipeline stages have better expression support, were you know which fields are existing in an expression.

So this will be the goal of this PR.

[Uzlopak]

I should Copy more Of the documentation into the jsdoc.

[vkarpov15]

Couple of minor comments, but LGTM in general. Worst comes to worst re: casting, we just add some any, but I think this change is great for autocomplete

[Uzlopak]

It should cover all expressions. It is purely based on the mongodb-Documentation.
I think we can risk to merge it. I assume, that we dont cover some edge cases. But it should be easily patched as we have tests and the typings are actually very clean implemented.

@mohammad0-0ahmad

[Uzlopak]

@vkarpov15
Can this be part of 6.4?

[vkarpov15]

Got a couple of minor comments but LGTM overall

[vkarpov15]

Do we really want to avoid linting benchmarks and website.js? Doesn't seem like the right thing to do, but I might be missing something

[vkarpov15]

Are these changes necessary?

[vkarpov15]

Can we get rid of the @version tags? It's a bit confusing because @version refers to the MongoDB server rather than the Mongoose version

[andreialecu]

Just a heads up that this PR broke a lot of our aggregations' typings, see more details in #11952

[andreialecu]

I opened #11956 to fix this.