Add additional Callgraph class inclusion filtering

[aburghuber]

What does this PR do?

Adds a nullable parameter called basePackageName to CallGraphAlgorithm#initialize that filters out all non-source classes from the graph (more accurately). Also adds AbstractCallGraphAlgorithm#includeCallToTarget for even more additional filtering.

The motivation behind this is that in Android projects often Android base API classes were included in the graph.

---

Checklist

Code style & guidelines

• I ran the formatter: mvn com.spotify.fmt:fmt-maven-plugin:format
• I added the necessary comments in the code
• I provided meaningful tests for my proposed change - Not needed
• I updated documentation (if needed)

Self-review

• I performed a self-review of my code
• I added or updated tests where needed
• I have successfully run tests with your changes locally
• My branch is up to date with develop

Review

• CI checks are green
• I requested a review from a core contributor

[JonasKlauke]

mmh I like the includeCallTarget method. But I think a Call object as parameter or the addition of the invoking statement would be better, so the users could also consider the stmt in the check.

i dont like the part about the base package. An application might not have one base package. We have also a similar approach with tagging a inputlocaction as Library. If it is tagged as Library then the call graph ignores it.
with a combination of your includeCallTarget method it should be possible to create your base package solution as an user.

So i would only partly accept this PR. However, thanks for improving SootUp