Collect some of the settings files in the log zip.

NOTE: We don't collect the network config since this could have
a wireless passphrase in it.
Add some status updates when saving channel remap data.
Create a valid pixelnetDMX config file if it doesn't exist already.

Somehow this was removed in 9890321d8.
(cherry picked from commit 4574597ced642cdf58f3557cb5fac5af356b5805)
Fix FPD config saving on Channel Outputs screen.
Remove dot after file numbers on file upload screen.

This seemed out of place.
Don't try to process callbacks for a plugin that doesn't have any.
Modify HexDump debug code to use standard logging.

HexDump() wasn't using our standard logging so it would not
show up in the log file.  This was mainly to allow HexDump()
to be used in binaries other than fppd.  This commit modifies
the logging code to have its own variable for the logfile name
and we set that whenever we load the settings file or parse
the command line arguments.  Now, we can use that filename to
determine whether to log to stdout or a file and the Log*
macros can be used in fpp and fppmm and any new binaries.
Dump the data sent to the FPD in a couple debug modes.

- Dump the config packet if logging at the debug level with the
  channelout mask set.
- Dump first 1024 bytes of a channel packet if logging
  at the excessive level with the channeldata mask set.
'#include "channeloutput/FPD.h"' to fix warning
Update stage binaries.
Add some error logging if wiringPiSPIDataRW() fails

Log the value returned and the number of bytes we tried to write.
Change the way we set the spidev buffer size.

spidev is no longer a module in the 3.10.x raspbian kernel
packages, so we need to set the buffer size in a different
way.

This should fix FPD output on FPP v0.3.0.

Thanks to Mat for the fix, I tested on my system and it
cures the FPD output errors, but we'll need someone with a
FPD to test and confirm the FPD is working again.
Merge branch 'stage' into multisync