Add __package_pkgng_freebsd type

Create __package_pkgng_freebsd type to handle package management via pkg-ng
Add explorer to __package to determine if "pkg" exists on the remote freebsd system
Expand logic within __package/manifest to determine which freebsd package manager to use
I don't know of anything particularly obvious. I get data like:

php5-5.4.32                    PHP Scripting Language
php5-calendar-5.4.32           The calendar shared extension for php
php5-curl-5.4.32               The curl shared extension for php
php5-gettext-5.4.32            The gettext shared extension for php
php5-iconv-5.4.32              The iconv shared extension for php
php5-pdo-5.4.32                The pdo shared extension for php
php5-pdo_pgsql-5.4.32          The pdo_pgsql shared extension for php
php5-pgsql-5.4.32              The pgsql shared extension for php
php5-xml-5.4.32                The xml shared extension for php
pkg-1.3.7                      Package manager
pkgconf-0.9.6_1                Utility to help to configure compiler and linker flags

from "pkg info."
The awk filter is just to get rid of spaces/description data. Sed is used to get the format of name:$name ver:$ver so that grep can find exact package names properly.

Examples of why this is needed would be a package p5-Net-Traceroute-PurePerl already existing on $__target_host with __package p5-Net-Traceroute (a completely separate package) slated for installation in the manifest.

Perhaps echo "$PKG_OUTPUT" | egrep "^${name}-[^-]+ " | sed -E -e 's/^.+-([^- ]+)[ ]+.*/\1/g' would do the trick, but that strikes me as significantly less human-readable for code maintenance. I could go either way you want on this one.