Consider module names for Gecko profiler resources #161299

Feature or enhancement

Problem

The Gecko reporter in profiling.sampling currently uses source file basenames for resource names.

When different packages contain files with the same basename, such as pkg_a/__init__.py and pkg_b/__init__.py, their resources may receive identical names, such as Resource: __init__.py.

This can make resources harder to distinguish when inspecting Gecko profiler output.

Proposed improvement

Consider using module names instead of source file basenames for Gecko resource names, so resources from different packages can be more easily distinguished.

This issue follows the discussion in #160982. That PR addresses preserving full source file paths in the function table; resource naming is a separate concern.

Has this already been discussed elsewhere?

I have already discussed this feature proposal on Discourse

Links to previous discussion of this feature:

#160982

Linked PRs

• gh-161299: Resolve Gecko profiler resources to module names #161310