feat(noUndeclaredDependencies): add availability restriction based on dependency type

[siketyan]

Summary

This pull request adds dependency availability restriction based on their type and the file path.

For example, we don't want to allow imports from vitest outside the test suites:

{
  "options": {
    "devDependencies": ["**/*.test.ts"]
  }
}

When this option is set, dependencies in devDependencies will be considered it's available only in **/*.test.ts files.

Inspired from import/no-extraneous-dependencies.

Test Plan

See added test snapshots.

[codspeed-hq]

CodSpeed Performance Report

Merging #4376 will not alter performance

_{Comparing siketyan:feat/noUndeclaredDependencies_devDependencies (2673379) with main (3401663)}

Summary

✅ 99 untouched benchmarks

[arendjr]

Nice work!

[siketyan]

@arendjr @Conaclos Thank you for your review! I've added commits to resolve the suggestions.

[siketyan]

@ematipico could you please take a look this (and merge if no problem) when you have time? No hurries, just a friendly reminder :)

[ematipico]

Awesome work! ❤️ I left some suggestions for the docs, then we can merge it

[ematipico]

Suggested change

	/// You can also use an array of globs instead of literal booleans:
	/// ```json
	/// {
	/// "options": {
	/// "devDependencies": ["**/*.test.js", "**/*.spec.js"]
	/// }
	/// }
	/// ```
	///
	/// When using an array of globs, the setting will be set to `true` (no errors reported)
	/// if the name of the file being linted (i.e. not the imported file/module) matches a single glob
	/// in the array, and `false` otherwise.
	/// You can also use an array of globs instead of literal booleans.
	/// When using an array of globs, the setting will be set to `true` (no errors reported)
	/// if the name of the file being checked (i.e. not the imported file/module) matches a single glob
	/// in the array, and `false` otherwise.
	///
	/// TODO: explain the example here
	///
	/// ```json
	/// {
	/// "options": {
	/// "devDependencies": ["tests/*.test.js", "tests/*.spec.js"]
	/// }
	/// }
	/// ```
	///

[ematipico]

I left a TODO at line 67. Usually, in our docs, we follow this pattern:

• explain the options
• explain the example
• show code of the example

The TODO should explain the example of the code. Also, I removed **/ because it usually matches too much and replaced it with a more simple glob

[siketyan]

@ematipico Thank you for your suggestion! Applied in ba4e63d. (Also merged main resolving conflicts)