WorkAround For Cannot Save BadVI Error. Drop lv21 and Add lv25 for Building.

[Karthick-Selvam-17]

• [ x] This contribution adheres to CONTRIBUTING.md.

TODO: Check the above box with an 'x' indicating you've read and followed CONTRIBUTING.md.

What does this Pull Request accomplish?

Justification:

• To resolve the "Cannot save a Bad VI without its Block Diagram" error during the build process in LabVIEW 25, we enabled the "Allow Debugging" option in the Engine Targeted project's build specification, which allowed us to achieve a successful build.
• Following this, LabVIEW team recommended a workAround to resolve the Cannot Save a BadVI error which is replacing Property Nodes in the project with their corresponding read accessor VIs wherever they are used to access data member values.

Implementation:

• Removed Allow Debugging Option.
• Based on error logs, we identified that this specific Initialize Instrument Engine VI causing the error of cannot save a BadVI.
  So, Applied the WorkAround in this VI, where We have replaced the Property Node with the appropriate read accessor VI.
• Dropped Lv2021 Build.
• Added LV2025 Build.

Why should this Pull Request be merged?

Required for future release.

What testing has been done?

PR Build.

[niveristand-diff-bot]

Bleep bloop!

LabVIEW Diff Robot here with some diffs served up hot for your pull request.

Notice something funny? Help fix me on my GitHub repo.

Instrument Addon Engine.lvlib--Initialize Instrument Engine.vi.png