Installing deployed code modules should use smarter filtering

## Describe the problem
When installing a module without specifying the exact version, IPM will default to the latest available one, even when there's deployed code platform limitations.

## Describe the solution
If a module is packaged as deployed code, i.e. specific to an IRIS version, then `install` should automatically filter to look for a version compatible with the current IRIS version. The convention for version naming is `__`, e.g. `1.0.0__2025.1`

## Describe alternatives
Forcing the user to always specify the actual version.

## Additional context
Related to #760