[eslint-patch] Improve performance and correctness of eslint-bulk-suppressions

[dmichon-msft]

Summary

Fixes #5054
Fixes #5006

Fixes an issue with incorrect computation of scope ids that were resulting in overly broad suppressions.

Details

• Simplifies the patching logic to load ESLint's linter.js into memory and only override Linter.prototype.verify, without generating any temporary files.
• Uses AST traversal to find the relevant node instead of extracting it from the reporter, due to limitations of data visibility. However, the new version only processes reported problems that aren't already suppressed via inline comments.
• Adds a new environment variable ESLINT_BULK_ESLINTRC_FOLDER_PATH that, if specified, short-circuits the patch searching for .eslintrc.js from every single file.
• Updates @rushstack/heft-eslint-plugin to set ESLINT_BULK_ESLINTRC_FOLDER_PATH to the parent of its detected ESLint config.
• Adds a tag eslint-tests to the ESLint test projects to make them easier to run
• Updates the ESLint bulk suppressions test project to run the suppression tester as well

How it was tested

Ran in the ESLint test projects.
Linked this version of the patch into a repository that has tons of bulk suppressions and ran it there.
Profiled this version vs. the old, for the projects tested the latency was cut roughly in half, though the AST walk is now most of the cost.

Impacted documentation

Behavior should be the same, other than ensuring that the suppressions from this feature show up in the output of getSuppressedMessages().

[dmichon-msft]

Suggested change

	suppressions.push(suppression);
	if (!serializedSuppressions.has(suppression)) {
	suppressions.push(suppression);
	}

[dmichon-msft]

This is producing suboptimal results when the desired position is inside of a comment. Additional logic will need to be added to detect which node a comment is associated with.