IPM Version Reported may be Inaccurate for some Namespaces when Mapped Globally

## Describe the bug
If IPM installed then mapped globally, this adds a package mapping to all Namespaces and will update the version of IPM installed in each Namespace to match. However, if IPM is updated or reinstalled, this may change the version of IPM running in all Namespaces, but version may only be updated in the Namespace running install.

## To Reproduce
Steps to reproduce the behavior:
1. Install non-latest version of IPM with 'zpm "install zpm "'
2. Map globally with 'zpm "enable -map -globally"'
3. Observe matching versions for all Namespaces when running 'zpm "version"'
4. Run 'zpm "install zpm "'
5. Observe only Namespace that updated IPM shows new version with 'zpm "version"'

## Expected behavior
If %IPM package is updated in all Namespaces, version reported in each Namespace should reflect this.

## System information (please complete the following information):
- IPM version: updating 0.10.3 -> 0.10.8
- IRIS version: IRIS for UNIX (Red Hat Enterprise Linux 9 for x86-64) 2025.1.1 (Build 313_1U) Tue Aug 26 2025 17:20:09 EDT
- OS: Unix

## Additional context
See example version output when one Namespace updated to 0.10.8:
LSCUCA> zpm 0.10.8
PLAZA> zpm 0.10.3
FOUNTAIN> zpm 0.10.3
Installed In: PLAZA
USER> zpm 0.10.3
Installed In: PLAZA

Reproduce the issue with the listed zpm install, enable -map -globally, and version commands across multiple Namespaces. Trace the global package-mapping and version-reporting entry points to determine why only the installing Namespace changes. Done means updating %IPM causes zpm version to report the new version in every affected Namespace.

Written by the indexing model from the issue text.