add spec_system test for issue #4

This doesn't reproduce though, when testing with puppet 3.3.0 on centos 6.4

    ================================================================================
    Package            Arch     Version                Repository             Size
    ================================================================================
    Installing:
    puppet             noarch   3.3.0-1.el6            puppetlabs-products   1.1 M
    Installing for dependencies:
    augeas-libs        x86_64   0.9.0-4.el6            base                  317 k
    compat-readline5   x86_64   5.2-17.1.el6           base                  130 k
    facter             x86_64   1:1.7.3-1.el6          puppetlabs-products    85 k
    hiera              noarch   1.2.1-1.el6            puppetlabs-products    21 k
    libselinux-ruby    x86_64   2.0.94-5.3.el6_4.1     updates                99 k
    ruby               x86_64   1.8.7.352-12.el6_4     updates               534 k
    ruby-augeas        x86_64   0.4.1-1.el6            puppetlabs-deps        21 k
    ruby-irb           x86_64   1.8.7.352-12.el6_4     updates               313 k
    ruby-libs          x86_64   1.8.7.352-12.el6_4     updates               1.6 M
    ruby-rdoc          x86_64   1.8.7.352-12.el6_4     updates               376 k
    ruby-rgen          noarch   0.6.5-1.el6            puppetlabs-deps        87 k
    ruby-shadow        x86_64   1.4.1-13.el6           puppetlabs-deps        11 k
    rubygem-json       x86_64   1.5.5-1.el6            puppetlabs-deps       763 k
    rubygems           noarch   1.3.7-1.el6            base                  206 k
    Updating for dependencies:
    libselinux         x86_64   2.0.94-5.3.el6_4.1     updates               108 k
    libselinux-devel   x86_64   2.0.94-5.3.el6_4.1     updates               136 k
    libselinux-utils   x86_64   2.0.94-5.3.el6_4.1     updates                81 k
do client/server rspec:system to reproduce issue #4

If we don't go via a master (so apply only) then the resource reference stays a
resource.  In 3.3.0 it gets turned into a string, and our code leaves it as a
string, becuase of dumbness.
Map correctly from string to resource in 3.3.0 #4

resource reference to actual resource changed in 3.3.0 when using
a master.  it comes over as a String now, so handle that.

This patch the resolve_resource method and adds the additional
conditionals required to that, as all the conditional stuff was
starting to get messy as heck.
Merge branch 'issue_4'
ship 0.4.2