debug: Add extra debug logging along Gradle analysis path

[elldritch]

Overview

This PR adds extra debug logging along the Gradle analysis path, to help solve user issues for ZD-7543.

Acceptance criteria

Enough logging to understand where dependencies are being filtered out.

Testing plan

I didn't, seems low risk, especially since the logging carrier explicitly ignores SevDebug when not in debug mode.

Risks

I'm worried about performance implications, but IgnoreDebugC seems to have already taken that into account.

References

• https://fossa.atlassian.net/browse/FDN-97
• https://fossa.zendesk.com/agent/tickets/7543

Checklist

• I added tests for this PR's change (or explained in the PR description why tests don't make sense).
• If this PR introduced a user-visible change, I added documentation into docs/.
• If this PR added docs, I added links as appropriate to the user manual's ToC in docs/README.ms and gave consideration to how discoverable or not my documentation is.
• If this change is externally visible, I updated Changelog.md. If this PR did not mark a release, I added my changes into an # Unreleased section at the top.
• If I made changes to .fossa.yml or fossa-deps.{json.yml}, I updated docs/references/files/*.schema.json AND I have updated example files used by fossa init command. You may also need to update these if you have added/removed new dependency type (e.g. pip) or analysis target type (e.g. poetry).
• If I made changes to a subcommand's options, I updated docs/references/subcommands/<subcommand>.md.

[csasarak]

I'm approving to not block since I think there's low risk here. But please have a look at my comments. Thanks for adding these!