fix(symbolizer): Device driver misattribution

[rabbitstack]

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

EnumDevices() captures driver base/size at startup. If between enumeration and and the first call stack capture, any driver shifted or reloaded, the base addresses in devs are stale. The address range check could match the wrong driver if two drivers happen to have overlapping or adjacent ranges in your stale snapshot vs. reality.

Mitigation steps:

• Validate cache hits against current devs
• Remove a stale driver if the new driver lives at the same base but a different device path

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?

---