fix: support OTA updates for devices with multiple image types

[AlexisPolegato]

Problem

Some Zigbee devices embed multiple MCUs, each with its own firmware and imageType. Z2M is unable to handle them
correctly because #inProgress and #lastChecked were keyed by ieeeAddr alone — the second imageType was either blocked
or silently ignored for 24h after the first update.

Open issues : #29293 #30022

Solution

• Composite key ${ieeeAddr}_${imageType} for #inProgress and #lastChecked, so each imageType is tracked independently.
• Reset #lastChecked after a successful update, so sibling MCUs are rechecked on their next queryNextImageRequest
  without waiting 24h.
• Conditional re-interview — only triggered if no other update is in progress for the same device.
• Pending request cache — if a manual update targets the wrong MCU first (toVersion === undefined), Z2M retries using
  a cached queryNextImageRequest recorded during the last auto-check.

[Nerivec]

Quick first glance:

• shouldn't use mixed keys in same map, it's confusing, prone to errors, and is defeated in logic anyway in both "has request" and "pending request" cases. The "has request" should use a separate Set (O(1) * 2), and "pending request" would appear to be far more efficient using just address instead of requiring startsWith
• shouldn't spread maps/sets, defeats the perf gains