check goes by default into the promise overload

[SimoneGianni]

When writing something like the following:

function getSomething<T>() :T {...};

// ...

check(getSomething(), is.object.matching({...}));

Typescript will infer this signature:

(alias) check<unknown>(obj: Promise<unknown>, matcher: unknown): Promise<unknown> (+4 overloads)
import check

Because it will for some reason infer:

(alias) getSomething<Promise<never>>(): Promise<never>

This is a problem cause it triggers eslint rule about promises having to be awaited, and each check in the tests gets the warning even when it is not actually dealing with a promise but merely with an inferred type.

This could happen because of the order of the check overloads, having the promise based ones before the others.

Check:

1. Why such ordering is necessary, eventually if inverted what would stop working properly (I suspect await check(async () => ..., is.throwing(...))
2. If it's possible to use a negated promise type to force typescript to use another overload unless the method is really really returning a promise