Update Undine to use Precise instead of Lucid

Just noticed this morning. Good catch!

I'm not sure about just upgrading the 1.x branch wholesale, since anyone on Enterprise prior to today will still be on Lucid. I'd feel a lot more comfortable with a 2.x branch running Precise once the 1.x branch becomes more stable and feature-complete, however. That way we could develop against 2.x and backport where necessary. Open to ideas on this, though.

After reviewing the patch, I'm glad to see the start of a solution to the config file problem, though I've split it off into its own issue: #2271871: Improve Undine's initial setup and configuration

This is how I plan to resolve the issue:

1) Get the 1.x branch release-ready using Lucid. The bulk of people already on Acquia are still using it.
2) Once released and stable, a 2.x branch will use Precise.
3) All future development will then be against 2.x, then backported to 1.x where applicable.

In short, moving to Precise is effectively blocked until we can say Undine is stable. The faster we get through the rest, the faster we get to the next major version.

Picking this back up, now that just about everyone on Enterprise has been moved to Precise. Given the current state of the project, it now makes the most sense to tackle this before the rest is stable.

The new required base box will be the precise64 base box provided on vagrantbox.es. This means that Undine will now require 64-bit support, whether native or through hardware emulation, though the trade-off in introducing a new requirement is well-worth maintaining environment integrity in this instance. This also means that existing installs will need to go through the `vagrant box add` process again, following with `vagrant destroy -f; vagrant up` to rebuild using the new base box.

Commit and new alpha release to follow shortly.

Committed the necessary changes to the PPAs, along with updates to the documentation and source Vagrantfiles. Note that users will need to update their own Vagrantfiles to use the precise64 base box instead of lucid32 by updating the following line, and rebuilding their environments with `vagrant destroy` and `vagrant up`:

  config.vm.box = "precise64"