fix(symbolizer): Introduce per-process module maps

[rabbitstack]

What is the purpose of this PR / why it is needed?

Previously, symbolizer had a cache of all modules involved in call stack frames. The map of modules was designed by indexing the module path to module info. This could lead to bogus symbolization outcomes if the module is unloaded on the base address that is later recycled to load a new module.

To mitigate this problem, the symbolizer holds a per-process module map.

What type of change does this PR introduce?

---

Uncomment one or more /kind <> lines:

/kind feature (non-breaking change which adds functionality)

/kind bug-fix (non-breaking change which fixes an issue)

/kind refactor (non-breaking change that restructures the code, while not changing the original functionality)

/kind breaking (fix or feature that would cause existing functionality to not work as expected

/kind cleanup

/kind improvement

/kind design

/kind documentation

/kind other (change that doesn't pertain to any of the above categories)

Any specific area of the project related to this PR?

---

Uncomment one or more /area <> lines:

/area instrumentation

/area telemetry

/area rule-engine

/area filters

/area yara

/area event

/area captures

/area alertsenders

/area outputs

/area rules

/area filaments

/area config

/area cli

/area tests

/area ci

/area build

/area docs

/area deps

/area evasion

/area other

Special notes for the reviewer

---

Does this PR introduce a user-facing change?

---