cherry-pick: "Revert "Add a copy of the updater binary to the recovery resources""
No longer necessary when a legacy property environment is available.
from @mdmower
cherry-pick: "Make legacy prop environment available to recovery"
Google changed the in-memory format for storing properties in 4.4.
Zips containing an older update-binary expect the old format, otherwise
assertions on properties in the update script fail.
This is just enough of the old property service to copy the properties
to the legacy format before running the updater.
Note: this commit is amended by @mdmower from the original version by
_that to only provide the prop system. Edits to install.c are done in a
separate commit from scratch to maintain apache2 licensing in this repo.
cherry-pick: "Use legacy property environment if old update-binary"
Instead of falling back to a provided binary when an installation
package contains an incompatible update-binary, set a legacy property
environment. This should increase compatibility with older update
packages while still using the new property system for supported
installation packages.
Method of setting prop environment based on cyanogen's commit:
"Set ANDROID_PROPERTY_WORKSPACE in exec." Tip to rename
/dev/__properties__ so that the legacy property workspace is actually
used comes from conversation with _that.

patch by @mdmower
6.23.2

thanks @mdmower we spared 160 kb on final packed recovery.img