New opd slimrom patches
implement apk_was_copied and APKID to fix apk handling

This uses $APKID as a working copy of $AID, all the apks. This better
handles the times when a prepatched apk is copied as a binary...this removes
the apk from the rebuild list while leaving it on the master list to be
included in the update.zip.

The $apk_was_copied allows us to also copy over an apk if patching succeeds but
apktool chokes out on us. It is set when an apk is copied and then skips the
rebuild line, avoiding the overwriting scenario we had before.
Version to 2.9.8

Includes apk handling and the fix for disappearing apks. Also new OPD patches
for slim and evervolv
New opd slimrom patches
Change 'readlink -f' to abspath method call to keep compatible with BSD readlink on OSX systems.
Fix mateor/auto-patcher#108 and replace backticks with .
AUTO_UPDATING feature, .config implementation, and versioning for patches.tgz

Maintainers and Contributors!
 :There is also a new variable PATCHES_VERSION, which must be incremented EVERY
time there is changes to ANY patches. Since we sometimes edit older patches,
I intend this variable to be set as equivalent to the date of the edit.

This commit sets up a .config file, with two current values
  AUTO_UPDATE=true
  PROUCTION=true
PRODUCTION is currently unused, I have it in mind for a test suite.
AUTO_UPDATE is fully implemented for Darwin/Linux. Cygwin/ApG users can test
this feature by uncommenting line ~1005, AUTO_UPDATE=false.

This feature checks if the user's branch is behind origin/master, and if so
merges that branch, if it can communicate with github (network access). The
script is then ran again, checking to see if batch.sh is needed to integrate
new patches and if so, running it.

Users who edit their own patches/script will find this feature troublesome.
It can be disabled by setting the AUTO_UPDATE key to false in the .config file.

There is a new temp file, .updated.log, which holds the merge and update info
to be added to the final logfile. Neither this nor the .config file is under
version control by design.

If the git pull fails (auto_update_error) I am unhappy that the logfile is so s$
of the rom probe information to run in this case, but ONLY if fails...I don't w$
twice in case of successful updates, etc.
Merge branch 'master_auto_update_merge'

Conflicts:
	auto_patcher
New Pac-man OPD patches

Guessinf Halo on 0610, could be a little later. If they post logs, I will adjust it.
Update PA telephony-common patch to better match

I still need to fix the pa-jellybean-legacy branch somehow. And today, since the workaround
will conflict with auto-updating
versioning to 2.8.3 and update PAC and ParanoidAndroid OPD patches

Undo some of the crazy versioning from the auto-update testing