Create TypeScript compilation benchmark that we run automatically on PRs

[vkarpov15]

Thanks for submitting a pull request! Please provide enough information so that others can review your pull request. The two fields below are mandatory.

If you're making a change to documentation, do not modify a .html file directly. Instead find the corresponding .pug file or test case in the test/docs directory.

Summary

Issues like #10349 make me anxious about merging TS changes, because sometimes what looks like perfectly reasonable TS causes massive compiler slowdowns. This PR creates a new benchmark workflow that runs tsc --extendedDiagnostics several times on a simple script and parses the result. So we can at least have an automated spot check that a given TypeScript-related PR doesn't cause 5x the number of instantiations.

Also, I added some logic to store benchmark results on Mongoose's Atlas cluster, which will help provide some neat charts :)

Examples

[AbdelrahmanHafez]

LGTM, this is a great start for having a time series for benchmarks.
It's important that in the future we have our benchmark files as immutable, so for example, if we were to add another test case, we'd need to create a new file for it, and then the benchmarking logic should create data for each file separately, and save it in the results array.

That way we can compare the same test across multiple mongoose versions.
Thanks 👍