Consider @types packages for used dependencies as used even without TypeScript

[alexeyr-ci]

Bug Description

Currently @types/... packages for used dependencies are only considered to be used when the TypeScript parser is used:

depcheck/src/check.js

Lines 140 to 151 in 77fe0e2

	parser === availableParsers.typescript
	? // If this is a typescript file, importing foo would also use @types/foo, but
	// only if @types/foo is already a specified dependency.
	lodash(_dependencies)
	.map((dependency) => {
	const atTypesName = getAtTypesName(dependency);
	return deps.includes(atTypesName)
	? [dependency, atTypesName]
	: [dependency];
	})
	.flatten()
	.value()

I'd prefer to consider them used for all parsers (or at least have an option to), because they allow seeing the dependency types in the IDE while developing.

Code snippets

Where the dependency is used:

Any use of a dependency like `jest`

Where the dependency is listed in package.json:

// devDependencies
"jest": "x.y.z",
"@types/jest": "x.y.z",

Versions

• node -v: v18.17.0
• npm -v: 9.6.7
• depcheck --version: 1.4.7

Extra info

Any extra info you want to include. Thank you for the bug report!

BONUS POINTS: If you wish to help us debug further, the depcheck --json option will show more information. Check here in the README for documentation on json output.