Enhanced help for run and restore command

Many available parameters for the restore and
run commands were missing in the help info and so
also in the <tab-tab> completion.

Now we should have hopefully all useful parameters documented
for run and restore.

Also, the tab-completion for "backupclient" and "restoreclient" now
works as it calls ".client"

Signed-off-by: Marco van Wieringen <marco.van.wieringen@bareos.com>
Add command for doing a name resolution on client.

Resolve command now can resolve given hostname(s) on director, client
and storage daemon if specified.

examples:

* resolution on director:
   resolve www.bareos.com
   > gonzo-dir resolves www.bareos.com to host[ipv4:84.44.166.242]

* resolution on client:
   resolve client=gonzo.bareos.com-fd www.bareos.com
   > gonzo-fd resolves www.bareos.com to host[ipv4:84.44.166.242]

* resolution on storage:
   resolve storage=File www.bareos.com
   > gonzo-sd  resolves www.bareos.com to host[ipv4:84.44.166.242]

Fixes #181: Add command for doing a name resolution on client.

Signed-off-by: Marco van Wieringen <marco.van.wieringen@bareos.com>
Use ; to seperate fields in address instead of :.

Now that IPV6 is more and more common use a semicolon instead
of a colon as seperator for the different fields of an address.
Always print loaded plugins.
Add the still missing keyword for run and restore.
Allow restoreoptions to be specified with restore.
Some keywords are only allowed in fileselection mode.

We now always send the BNET_START_RTREE and BNET_END_RTREE signals
even when the api mode is not enabled. This way bconsole also knows
when its in file selection mode and the tab expansion can show the
only expand keywords allowed in a certain mode. e.g. no more cd
and ls expansion when not in file selection mode which leads to
the dreaded "*cd .lsdir: is an invalid command." and
"*ls .ls: is an invalid command."
Fail restore job when plugin options and no support.

When we need to send plugin options to a FD and it has a to low version
fail the restore job so the backup operator knows he needs to upgrade
its client (or disable the compatible option) of the target FD.
windows plugin directory created and set in cfg.

The windows installer now creates also a directory
for plugins, ususally C:\Program Files\Bareos\Plugins

Also, this directory is set in the plugin directory comment
in the default bareos-fd.conf

Also, we now have a "compatible=no" comment in the fd.conf
that tells the user that for new bareos features this has to
be set to no to disable the Bacula compatible mode.

Signed-off-by: Marco van Wieringen <marco.van.wieringen@bareos.com>
Fixed wrong directory for plugins in nsi installer

We created the Plugins Directory in the wrong location
before.

Now that is fixed

Signed-off-by: Marco van Wieringen <marco.van.wieringen@bareos.com>