Fix built-in context typing for newTracker (closes #1089)

[Peter Perlepes (igneel64)]

Fix context option typing for newTracker

Allow for passing either webPage or session options as expexted.
Adds the BuiltInContexts type.

Notes

• Add the RequireAtLeastOne helper for types. (Could prove useful in the future for the whole project) Rightfully stolen from @azure
• Some typos

closes #1089

[Matus Tomlein (matus-tomlein)]

This is really cool, I didn't know about the trick!

I'm just wondering if it is a breaking change? Technically it might break the build for some users in case they set an empty dictionary in their apps? If so, strictly speaking we should add this to the next major release instead of a minor. (btw, don't forget to change the base branch to a release branch before merging)

[Matus Tomlein (matus-tomlein)]

Some of the typos are quite funny :D

[Paul Boocock (paulboocock)]

Have you never tried to Condifugrate your trackers before?

[Peter Perlepes (igneel64)]

This is really cool, I didn't know about the trick!

I'm just wondering if it is a breaking change? Technically it might break the build for some users in case they set an empty dictionary in their apps? If so, strictly speaking we should add this to the next major release instead of a minor. (btw, don't forget to change the base branch to a release branch before merging)

Accounted for people that could have added {} as the input on contexts. This makes it a non breaking change.
(Will add a PR for next major release to remove it completely)