Work on clarification for LVAddons documentation

[svelderrainruiz]

That's a great start @svelderrainruiz, thanks a lot for doing that!
I'm also particularly interested in the PPL section when it's available.
Everything else seems pretty clear except for the "Per-target LibraryPaths" in the "Location of LVAddons" section, which I don't understand how to use. An example would be helpful.
As a more general comment, examples are likely appreciated everywhere for everything that can be set or customized, so there might be something to improve there IMO.
Another note, regarding the "SupportedBitness" JSON attribute. The documentation doesn't say if it is a String or Numeric datatype. Again, an example would clarify this.
Thank you so much!

Originally posted by @matthiasbaudot in https://github.com/ni/labview-icon-editor/discussions/105#discussioncomment-11614136

[svelderrainruiz]

@eyesonvis tagging you for visibility

[svelderrainruiz]

We need to add the following example:

Example 1
Problem statement
A system has 2 different LabVIEW versions (2024, 2025) on both 32 and 64 bits. The system owner wants to install the open-source version of the icon editor for each of the LabVIEW installations he has, without having to make changes to the LabVIEW installation files each time he decides to upgrade the icon editor.

Solution -
Create VI Package that installs a 32- and 64-bit PPL of the icon editor into the LVAddons location and creates the necessary folder structure and JSON files so that all 4 LabVIEW installation paths load the icon editor from LVAddons instead of resources folder

[svelderrainruiz]

Main examples would be bitness specific files like dlls or ppls. Rather than making multiple addons with supportedbitness set, you can put use the target directories to segregate those files within one addon.