move scripting libraries on disk to make reuse easier

[dbendele]

Is your feature request related to a problem? Please describe.
Scripting APIs for Import, ARINC 429, Shared, and Ballard should be organized on disk during export and installation to promote reuse without requiring installation of unnecessary packages.

Describe the solution you'd like
I would imagine the ARINC 429 library, Import library, and Shared being located at VeriStand Custom Device Scripting APIs/ARINC 429 and the Ballard 429 library going to VeriStand Custom Device Scripting APIs/Ballard/ARINC 429. Again, it doesn't have to be done for this PR, unless it makes it easier on you. The main idea is to keep the generic ARINC 429 libraries separated from the Ballard library so we can reuse them for other custom devices.

Describe alternatives you've considered
Status quo dumps all scripting libraries under Ballard/ARINC 429

Additional context
Installation directory structure reflects built structure. It is pretty easy to change the example project dependencies if we later decide to change the structure. I would like to build the palette soon, and that is very coupled to the installation file structure but can be changed easily enough using the palette API. Do you have a vision for what you want the structure to look like on disk?

This also makes it much easier to create the two separate nipkg files outlined in the design spec. If the files are in different top-level locations, it makes building the packages much easier.

[Karl-G1]

No need to do this for the first release.