[Package Issue]: Move IronmanSoftware.PowerShellUniversal to Devolutions.PowerShellUniversal

Nobody has claimed this yet.

### Please confirm these before moving forward

- [X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- [X] I have not been informed if the issue is resolved in a preview version of the winget client.

### Category of the issue

Other

### Brief description of your issue

Ironman Software was acquired by Devolutions, and we now build and release PowerShell Universal.
The package is still published as `IronmanSoftware.PowerShellUniversal` and stuck at 5.0.0 from
August 2024, while the product is at 2026.2.4. We'd like to move it to
`Devolutions.PowerShellUniversal`, next to the other packages we publish under `d/Devolutions/`.

Two PRs are already up following the FAQ:
[#419031](https://github.com/microsoft/winget-pkgs/pull/419031) (new identifier) is green.
[#419030](https://github.com/microsoft/winget-pkgs/pull/419030) (transitional, old identifier) is flagged and shouldnt
`Manifest-Metadata-Consistency` for a missing `ProductCode` but that's deliberate, the FAQ says not
to declare it on the transitional version.

Anything you'd like changed before these can be merged? And should the old versions stay in
`i/IronmanSoftware/`, or be removed?

### Steps to reproduce

Not a client bug — asking for guidance on a package move.

Start with the winget package-move FAQ and review PRs #419031 and #419030, including the reported ProductCode check. Confirm the requested identifier transition and treatment of existing i/IronmanSoftware manifests against repository guidance; done means maintainers have answered the questions and the applicable PRs are merge-ready.

Written by the indexing model from the issue text.