Implemented iterative deploy framework and iOS specific implementation
When utilizing iterative deploy in conjunction with incremental cooking only the changed items are pushed to the device resulting in potentially far faster iteration times.
#ios
#codereview daniel.lamb, marcus.wassmer, chris.babcock, josh.adams
[CL 2386082 by Peter Sauerbrei in Main branch]
- Add checking of validity dates on mobile provisions and signing certificates, choosing only ones that are currently valid
- Add extended logging for found mobile provisions and signing certificates, to help debug possible provisioning issues in the future
- Remove duplicated Apple chain certificates from DotNET/IOS and switch to using the ones in Engine/Build/IOS
- Various other output logging improvements and time stamps during code signing
- Remove rotted -interactive option and associated code
- Fix unused variable warning on mono
For release notes: iOS deployment from PC requires the machine date/time to be reasonably accurate (date/time checks are now in place to filter out expired mobile provisions and signing certificates, preventing various deployment issues, but they rely on the machine time being correct)
#codereview peter.sauerbrei, josh.adams
[CL 2268101 by Michael Noland in Main branch]
