Created menus as source code, not as VIPM artifacts. Updated build s…

[niACS]

…pecification.

GitHub Issue for the Pull Request

Link to the relevant GitHub issue

GitHub Discussions Related to this Pull Request

None

Checklists

Completing these checklists ensures that your PR meets our build server requirements on the first attempt. If you're unable to complete any of the following checks, please submit your PR as a draft to the best of your ability. We will provide any clarification you may need after posting it.

• [x ] I do not require assistance from NI to complete any of the following checks.
• [x ] The changes in this PR are based on the appropriate NI-repo feature branch
• I am submitting the changes in this PR to the appropriate NI-repo feature branch
• I built a VI Package using the Powershell build tool.
• I installed the VI Package produced by the Powershell build tool and tested my change.
• I tested my changes after installing the VI package.
• NI has my contributor license agreement.

I built and installed the VI package locally. I don't know the state or process for using the Powershell tool.

Summary of Changes

I added the appropriate menus to the correct menu folders, and disabled menu creation in the VIPM build specification. The following were modified or updated:
actorframework.mnu
_actorframework_experttools.mnu
_actorframework_msgqueuepair.mnu
_actor_framework_testsupport.mnu (new)
actorframework_controls.mnu (new)

Reason for Change

2026 Q1 shipped with the old palettes. These are the correct ones.

Visual Aids

Include any visual aids that would help the reviewer gain additional context.

Additional Information

Include any further details that may assist the reviewer in understanding the context of this PR.

Testing

This section describes the automated and manual tests performed for this bugfix/feature.

Manual Tests

Manual inspection. Yep, the new palettes are there.