Provide a means for build breaks to be reported.

This allows one to easily run "make build-bug-report" to
mail the bug report to interested parties.
Specify which form to use to add and edit users

That are several forms related to bsdUsers model, so we need to tell
which one to use.
Set GIT_PORTS for truenas.
Pull in TrueNAS gui/build under nas_source.

We will be modifying the build to pick files from
this directory instead of using the top level build.

Example would be 'build/files/install_sata_dom.sh',
this file will now come from
nas_source/truenas-components/build/files/install_sata_dom.sh.

And so we shall do it for all the other TrueNAS specific
files.
pbid needs a pbi directory, so let's give it one.
Add missing space to fix shell conditional.
Add icons for installed plugins as well
If mkisofs is not available, do not silently try to build and install the sysutils/cdrtools port.

Instead, error out, and allow the user to install it manually.
Create the sha256 signature right after creating the ISO.

There is duplicated logic in two other release scripts which
try to generate sha256 signatures, so we can get rid of
the duplicate logic in those places, in separate cleanup passes.
The other places are:

(1)  The /root/nightly.sh script.

(2)  The build/build_release.sh script.

Compute sha256 signatures for the full image and GUI_Upgrade image right after we build them.

This will allow us to remove the logic for computing these signatures
from the build/build_release.sh script in a future cleanup pass.

Pull the steps for generating the sha256 signature out of the release script and push it deeper into
the build script, closer to where we actually generate the ISO and txz images.

Only write out sha256 signature to disk if computing sha256 signature succeeded.
When calculating the sha256 checksum of the GUI_Upgrade image, use the base filename, not the full filename path.
Fix this in the correct location.

- pbid needs a PBI_APPDIR, so let's give it one
Restart collectd when importing/decrypting a pool.
Scenario:
Assumption: There are both encrypted and unencrypted pools
1. FreeNAS boots and automounts unencrypted pools
2. collectd starts to track free space on the pools
3. User unlocks the encrypted pols
Before fix: collectd doesn't track free space of the "new" pools
After fix: collectd correctly starts tracking free space of the unlocked pools