Implement class filtering using regular expressions

[sohyun-ku]

related to #99

An optional feature is provided to filter classes using regular expressions.
Filtering is based on the result of packages, excluding excludedPackages, and adding additionalPackages.

[github-actions]

Scavenger Test Results

163 files  163 suites   1m 33s ⏱️
274 tests 262 ✅ 12 💤 0 ❌
292 runs  280 ✅ 12 💤 0 ❌

Results for commit 972d905.

♻️ This comment has been updated with latest results.

[taeyeon-Kim]

I think it's worth considering getting the packages setting as a regular expression.
What do you think of this suggestion?

[sohyun-ku]

@taeyeon-Kim

I agree with your suggestion.
What I was considering is we already have additionalPackages, excludePackages option.
so it seems necessary to prioritize them.

[taeyeon-Kim]

@sohyun-ku Okay good, that's about the same level of setup as you said.
But how about include~ rather than exclude~?? I think the negation has a downside that makes me think twice about it.

[sohyun-ku]

@taeyeon-Kim @kojandy

That's a good opinion, It's confusing to deal with only one case.
So I added it for both cases, and to make it more flexible, I modified it to a class path including the package.

[taeyeon-Kim]

👍 👍

[sohyun-ku]

Regular expressions are relatively computationally expensive, so they were placed later in the conditional statements to reduce unnecessary computations.