[Feature] Decouple VIPM custom install actions from Pre/post LVAddon LabVIEW versions

[svelderrainruiz]

Summary / Description

Technical debt in the Pre/Post LVAddons uninstall/install logic led to a regression in v0.2.0‑build590, causing at least three Discord users to revert their LabVIEW installs when the default Icon Editor appeared.

Motivation / Use Case

Decouple the install/uninstall logic from specific LabVIEW versions by having each VI Package select its custom actions at build time—enabling streamlined support for LabVIEW 2023+.

Proposed Solution / Feature Details

Create standalone custom-action VIs that would be injected into the VIPB build specification before building it.

Alternatives / Workarounds (optional)

No response

Possible Implementation (optional)

No response

Additional Context (optional)

I am making a recommendation to the Steering Committee for Icon Editor to publish our first revision of the Icon Editor to VIPM.

[svelderrainruiz]

[svelderrainruiz]

#318 is a dependency of this issue