consistent-type-imports: add autofix option to prefer inline type keyword

[jackfranklin]

import {FooWhichIsAType, BarWhichIsValue} from './some-file.js';

This will cause an error with consistent-type-imports, but the autofix for the rule will fix it like so:

import type {FooWhichIsAType} from './some-file.js';
import {BarWhichIsValue} from './some-file.js';

As of TypeScript 4.5, the following is also supported (https://devblogs.microsoft.com/typescript/announcing-typescript-4-5/#type-on-import-names):

import {BarWhichIsValue, type FooWhichIsAType} from './some-file.js';

I'd like to propose a configuration flag be added to consistent-type-imports to enable the auto-fixer to be configured to prefer either approach.

I'm very happy to work on this PR, if this is something you would be happy landing? Thanks!

[bradzacher]

Duplicate of #4338