(QE-519) beaker should raise error if host does not have a platform set

- beaker tries to do crazy things when hosts aren't on supported
  platforms, let's check that option right at the start
pre-release of 1.0.1 beaker
documentation for supported HOST settings
Merge pull request #79 from anodelman/make-gem

pre-release of 1.0.1 beaker
Add support for PE 3.2 with its new answers requirements
enforcing platform format of OS-VERSION-ARCH

- added spec tests to ensure that we correctly sort out bad platform
  names
- will need to write an associated patch to update our node
  configuration files to meet the new standard
Merge pull request #82 from branan/support_pe_32

Add support for PE 3.2 with its new answers requirements
make 1.0.1 gem
Merge pull request #83 from anodelman/make-gem

make 1.0.1 gem
move VagrantFiles into .vagrant_files directory of working directory
Merge pull request #80 from anodelman/hunner

move VagrantFiles into .vagrant_files directory of working directory
Merge pull request #72 from anodelman/check-platform-set

(QE-519) beaker should raise error if host does not have a platform set
Catch SystemCallError during blimpy provision for retry

Previously we were only catching Fog::Errors::Error exceptions, this patch
makes sure that system call failures are also caught, so things like connection
refused and no route to host which are generally transient, are caught and
retried properly.

Signed-off-by: Ken Barber <ken@bob.sh>
Merge pull request #84 from kbarber/maint/master/retry-blimpy-on-systemcall-errors

Catch SystemCallError during blimpy provision for retry
Add `test_manifest_on` and `test_manifest`

The old methods `apply_manifest_on` and `apply_manifest` enforced return
codes and would raise errors under certain conditions instead of
returning the stdout/stderr/exit_code for the testing library (rspec,
etc) to validate. It also required explicit return codes for testing
against failures.

This pull request:
- Creates a method `manifest_helper` which handles the logic for the
  following manifest methods
- Changes the name of `apply_manifest_on` and `apply_manifest` methods
  to `test_manifest_on` and `test_manifest` to reflect their behavior
- Defines methods `apply_manifest_on` and `apply_manifest` to be the
  same as before, but without the return code test enforcement
- Bugfixes the `:catch_failures` options argument and adds a
  `:expect_failures` argument for testing manifests.

This change is backwards incompatible.