hopeful fix to flight input showing autopilot controls
pilot controls will always be zeroed if there is no actuall pilot
split resources structure for single part and aggregate
we must respect the rules :P
Workaround to fix #448 and maybe #428

RemoteTechArchive.cs - Modified CheckRange to return true if the vessel
is currently in the prelaunch condition.  This prevents the archive from
showing as out of comm range during initial start up when RemoteTech
seems to have issues returning the correct value reliably.
BindingManager.cs - Added a null check before disposing the
flightControl variable.  I have had issues on and off with this throwing
null reference errors when reverting or going to the space center.
Use situation enum instead of converting to int

RemoteTechArchive.cs - Check vessel situation against the enum value
rather than converting it to an int first.
docs for 408 - direction suffixes
Move boot out of InitObjects

kOSProcessor.cs - moved call to shared.Cpu.Boot() out of InitObjects to
prevent errors in the boot script from killing OnStart.  Added a bool
firstUpdate to check for the first run of the update command and to boot
the cpu if it is.
Move boot to after setting firstUpdate to false

kOSProcessor.cs - flipped the order of setting firstUpdate to false and
running shared.Cpu.Boot();  If the boot script blocks from setting
firstUpdate to true, we don't want to try and boot repeatedly.
Rework boot file access process

kOSProcessor.cs - Rearranged the work flow for copying boot files to the
local hard disk.  The process is only started when creating a new local
hard disk.  If the hard drive node was removed from the save file, there
may be a new hard disk without this being the first launch.  To ensure
that we don't mistakenly copy a new boot file at that point, there is
also a check for PRELAUNCH situation.
CPU.cs - added a guard against trying to access the archive for boot
while out of comm range.  Vessels already in orbit but not in comm range
will not throw an exception on loading if the option to start on the
archive is enabled.
PersistenceExtensions.cs - Create another extension method which will
allow us to check if the archive is within range without a call to
CurrentVolume which will throw an error if out of RT comm range.  This
is only applicable when kOS is configured to start on the archive and
support remotetech.  Trying to access the archive any other way from
internal scripts (including a boot script) will still throw the error as
expected.
RemoteTechVoumeManager.cs - provide the base method used by the new
extension method added above.  Simply skips GetVolumeWithRangeCheck.
docs for new checkin
Merge remote-tracking branch 'hvacengi/remotetech-loading-workaround' into develop
Merge remote-tracking branch 'erendrake/resource_split' into develop
Merge remote-tracking branch 'erendrake/flight_input_isolation' into develop

Conflicts:
	src/kOS/Suffixed/FlightControl.cs
fixed merge
logging work
swapped out lame container count for more useful part list