Move application of Binary Artifacts Gradle Wrapper Action exception into checks/evaluation/

[ethan7g]

Is your feature request related to a problem? Please describe.
This is where the feature should be implemented so that log messages can reflect the exception, rather than having it be an opaque process for users. It would mean that raw/binary_artifacts returns the expected files, without special exclusions.

Describe the solution you'd like
Move the exception to checks/evaluation/binary_artifacts.go.

• Create log messages reflecting the status of the exception so that users can see details

Describe alternatives you've considered
Current stopgap implementation is opaque and solves the immediate issue by having raw/binary_artifacts exclude gradle-wrapper.jar files from being returned when the Action is detected.

Additional context
First mentioned in #2039.

[github-actions]

This issue is stale because it has been open for 60 days with no activity.

[github-actions]

This issue is stale because it has been open for 60 days with no activity.

[spencerschrock]

Completed as part of #3508