Fix the openwreck code to only kick in when speedtank = true

this allows the golem and other non-speed tanks to salvage/loot as they go
looteverything=false does NOT mean do not loot anything
it means loot aonly what you can loot without slowing me down
Merged in the mono command line options - YOU WILL NEED TO MODIFY YOUR QUESTOR STARTUP ROUTINE

This does include the chantling shedules.xml stuff. The syntax needed to start questor with the chantling scheduling code is:
Questor chantling character=blah
Latest merge with Da-Tech's master branch - directeve.dll and some "is target is the right target?" fixes

I'd love to know the "right way" to pull individual commits from other trees w/o losing the commit history, bah
Rename some local variables used in mission stats to be a bit more clear and avoid naming collisions with local variables elsewhere (not needed but looks cleaner)

Update FinishedTask timestamp when finishing a mission in all cases, before it was only updated in  BeginAfterMissionSalvaging. This should solve the negative mission times in the mission statistics.
Cleanup of log file (console) messages

Added distance to locking of wrecks and targets, but not to unlocking... which I may add later
Added target,Distance to the Log message when unlocking a target - might help with debugging odd occurrences

removed target.istargetedby --> unlock code from the new behaviors AttackClosestbyName and AttackClosest, these need further testing
Cache = Runtime Defined Values

Settings = User Defined Values

I also started enabling the local checking code. It needs some debugging to verify the new settings work.
At the moment it only logs what it sees in local... once I am happy that it is reliably working Ill enable it to hold in station until local is clear.
Change: Salvage.cs: In space do not pickup items that will not fit into a freight container unless they are a mission completion item (this mission), or a common mission completion item (other missions)

Change: UnloadLoot.cs. When unloading loot unload all the common mission completion items into your hangar (not configurable, they really need to be in your hangar to be accepted at mission completion)
Change: ItemCache.cs - certain mission completion items that are alive should be excluded from this list as we want to scoop them at all times.
Valuedump was not selling minerals... it is now.
fix an error in the local watch stuff that was keeping questor from compiling.
for some odd reason these delays were borking things on some systems...

I'll have to re-add them in with a similar style to the _pulse stuff, for now Im removing them and changing the _pulsedelay a bit which should help
Create the /log/charactername/pocketstats directory
Enable the wreck blacklist feature since ppl seem to be adventurous and doing so on their own...

Created settings in the character xml for Blacklisting small and medium wrecks.
Keep in mind that these settings do currently seem to be incompatible with the noctis and should only be enabled for debugging purposes until deemed stable.

by making this commit those that have enabled the feature can disable it or enable it on a per character basis
attempt to close the CCP downtime approaching message that doesn't seem to be closing with the old quote, that still looks right, shrug.
Adjust chantling scheduler to be more flexible with ppl that tend to run more than 12 hrs.
Actually enable the use of the new UnloadState.MoveCommonMissionCompletionItems State.

This moves all common mission completion items from your cargo to your hangar so that everything else could potentially goto a corp hangar or freight container.
Misc sync'ing with bbdays experimental tree

scheduler fix (hopefully)
correct warpoutstation to not require a globally unique bookmark name.
Hopefully resolve the "speed tank" is true and aftermission salvaging is on issue.

The new speed tank feature where we do not open wrecks at all caused a problem for the after mission salvaging. It should now be fixed.
make it more clear when log file are opened and created for those that may not realize where they are and when they are written to