Latest package / forceios modified to include smartsync for native apps

We can't nuke the unstable branch, because there are unreleased code changes in there.  Also, nuking branches like that is inconsistent with our git flow for our other repos, which just makes our git flow more complex and therefore more prone to mistakes.

I'm making a strong vote that we stick to the model that I've been using, unless there are equally strong objections to it.  I make permanent/legitimate—i.e. release+1 development—non-binary changes in unstable.  Then, when prudent/necessary (often immediately after said changes), I create new binaries, and stage them to a temporary branch.  This temporary branch is only ever unstable+1 commit, because there's no reason to keep a history for it.  And when we're done with it—i.e. the next time we build and overwrite the unstable+1 commit—the only unique data we lose are the nightly binaries themselves.

This system allows us to use the same git workflow as we use for our all-source branches:

- We can continue to promote `master` patches easily back to the official `unstable` branch.
- We can continue to develop in `unstable`, again easily pushing all changes up to `master` at once when we release, without carrying the baggage of "nightly" binaries forward with it.

In the absence of moving all of our binaries out to a CDN, I don't see a better way.