Support multi-module Android projects when sending Source Context

[wzieba]

Problem Statement

When sending Source Context via Sentry Gradle Plugin, I've noticed that the source is taken only from the main application module. This is problematic for multi-module setups, which are fairly common.

I've prepared a minimal reproduction project of what I have in mind.

Reproduction

An Android application with x app module and y its dependency: https://github.com/wzieba/SentrySourceContextMultiModule

Expected behavior

Running assembleRelease prepares source context bundle with all classes from x and all classes from y modules.

Current behavior

Running assembleRelease prepares source context bundle with only classes from x (proof: https://github.com/wzieba/SentrySourceContextMultiModule/actions/runs/8467510900/job/23198486580#step:5:20)

Solution Brainstorm

I think it could be addressed manually with additionalSourceDirsForSourceContext, but I haven't prepared a working solution yet. Ideally, It'd be great if SAGP could do this internally (maybe as a non-default option?).

[kahest]

Hey @wzieba thanks for the suggestion, I think this makes sense, but it's not our top priority at the moment

[markushi]

Let's investigate this first on our end, as in theory it should work:

1. Apply plugin to library modules as well (and disable all other plugin features)
2. Manually upload source context via gradle
3. Verify asset merging combines all bundle IDs
4. Ensure app sends proper bundle IDs

[romtsn]

The end goal would be for our gradle plugin to support applying on the root project level, so then we could have access to all modules, but this is a bit bigger initiative