Allow importing AVA as anyTest in TypeScript files

[pvdlg]

Fix #293

Change use-test to allow importing AVA as anyTest in order to account for the example in Typing t.context.

This change could be further improved by making sure that when AVA is imported as any it is assigned to a variable name test, e.g:

const test = anyTest as TestInterface<{foo: string}>;

In other words the following should be invalid:

import anyTest, {TestInterface} from 'ava';

const myTest = anyTest as TestInterface<{foo: string}>;

That's important because some other rules depends on the AVA object to be named test. However, the change in that PR is still better than forcing users to disable the rules.

Implementing such validation is beyond my knowledge of ESLint aPI though...

[novemberborn]

Implementing such validation is beyond my knowledge of ESLint aPI though...

I've opened #295 to track.

[turadg]

JSDoc in .js files is an increasingly popular way to use TypeScript. e.g.,

import anyTest from 'ava';
/** @type {import('ava').TestInterface<{ data: { kernelBundles: any, config: any } }>} */
const test = anyTest;

Any concerns with allowing anyTest in .js too? (i.e. removing the filename constraint)