A wrong behavior after upgrade to 4.14.0

[mlc-mlapis]

• I have tried restarting my IDE, and the issue persists.
• I have updated to the latest version of the packages.
• I have read the FAQ and my problem is not listed.

Repro

If AppState is imported:

import {AppState} from '@m-kbase/shared/general/states';

and later used only in a constructor, like:

constructor(
   private _store: Store<AppState>
) {}

then the warning appears in many places (in relation to the import {AppState} from '@m-kbase/shared/general/states'; line):

warning 'AppState' is defined but never used @typescript-eslint/no-unused-vars

Expected Result

The same result as with the previous version 4.13.0 or earlier, with no warnings.

Additional Info

Probably similar to #2946

Versions

package	version
@typescript-eslint/eslint-plugin	4.14.0
@typescript-eslint/parser	4.14.0
TypeScript	4.0.5
ESLint	7.18.0
node	12.13.1

[chunghha]

I see same warning after updating from 4.13.0 to 4.14.0. For example with this code, it throws "3:22 warning 'HealthResponse' is defined but never used @typescript-eslint/no-unused-vars",

import { Controller, Get } from '@nestjs/common';

import { AppService, HealthResponse } from './app.service';

@Controller('tfapi')
export class AppController {
	constructor(private readonly appService: AppService) {}

	@Get('/isHealthy')
	async getHealth(): Promise<HealthResponse> {
		return this.appService.getHealth();
	}
}

[vladimiry]

Same here. Btw, the warning doesn't get triggered in the case of inline type import use:

constructor(
   private _store: Store<import("@m-kbase/shared/general/states").AppState>,
) {}

[bradzacher]

Same as #2941, #2942, #2945

Fixed in #2943

Please use the search next time.

[mlc-mlapis]

@bradzacher Thanks for your PR, I was too fast. You are right. 🥇