Create release workflow that uploads a distribution artifact for easier consumption in LV installers

[KSharma-NI]

GitHub Issue for the Pull Request

N/A

GitHub Discussions Related to this Pull Request

N/A

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.

• I do not require assistance from NI to complete any of the following checks.
• 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.

Summary of Changes

This PR introduces a repostory-specific action that builds a distribution artifact whose directory structure is similar to the structure in the LabVIEW installer.
The relative structure in the artifact now looks like:

- menus
   - Categories
   - Controls
- resource
   - AFDebug
      - DETT Format
      - Protected Actor Handle
      - Register Actor Msg 
   - Framework
      - Providers
         - ActorMessageMaker
         - AddActor
         - AddActorInterface
         - GProviders
         - MessageMakerProvider
         - MessageRescripter
- vi.lib
   - ActorFramework

Reason for Change

As part of the NI's open-source initiative, it was decided to consume artifacts from GitHub and have the artifact with its relative structure similar to the latest LabVIEW installers. This makes it easier to while include Actor Framework with the installer.

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

Existing Unit tests in AzDo passed without errors:

Manual Tests

In addition to the Unit tests, the INIs and VIs between AzDo and the develop branch were also compared. They were similar.