Loosen @typescript-eslint/naming-convention rule to allow more formats for import names

[Mrtenz]

The bump to a more recent version of the TypeScript ESLint plugin added support for specifying naming conventions for import names (import name from 'package';). We didn't add a case for this, so the default format of camelCase applied, meaning that this is not allowed:

import SomeClass from 'some-package';

I've updated the rule to allow camelCase, PascalCase, snake_case, and UPPER_CASE, since the names of imports can depend on the (3rd party) package, and it feels unnecessary to enforce more strict formats in this case.

[Gudahtt]

Note that we could still alias the imports, so we're not beholden to package authors completely here.

But still, loosening this seems harmless to me, LGTM

[Mrtenz]

Note that we could still alias the imports, so we're not beholden to package authors completely here.

True, but in the case of class imports for example, we'd want to use PascalCase, which previously wasn't allowed.