(PUP-2349) Add windows specific expectation for deprecation_warning

Previously, the spec test assumed that no deprecation warnings would be issued.
However, the test relies on puppet using the `source_permissions` of the
source, and that behavior is deprecated on Windows. As a result, the test
was failing on Windows.

This commit updates the test to expect only the "Copying owner/mode/group/.."
deprecation warning on Windows, and no deprecation warnings on other platforms.
(PUP-2349) Add windows specific expectation for deprecation_warning

Previously, the spec test assumed that no deprecation warnings would be issued.
However, the test relies on puppet using the `source_permissions` of the
source, and that behavior is deprecated on Windows. As a result, the test
was failing on Windows.

This commit updates the test to expect only the "Copying owner/mode/group/.."
deprecation warning on Windows, and no deprecation warnings on other platforms.

Reviewed-by: Josh Partlow <joshua.partlow@puppetlabs.com>
(PUP-3069) Fix path expansion for environment.conf test on Win

The intention in these specs is for the default_manifest setting
to be absolute for the platform under test.  Without an expand_path,
the POSIX style setting we're using will still seem relative on
windows, causing these two tests to fail.  Really these settings
should only be used on a master instance, which would be POSIX,
but for completeness sake, this commit expands the initial
default_manifest paths.
Merge branch 'feature/master/pup-3069-win-spec-fix'

* feature/master/pup-3069-win-spec-fix:
  (PUP-3069) Fix path expansion for environment.conf test on Win
Merge branch 'master' of github.com:puppetlabs/puppet

* 'master' of github.com:puppetlabs/puppet:
  (PUP-3069) Fix path expansion for environment.conf test on Win
  (PUP-2349) Add windows specific expectation for deprecation_warning
(maint) Expect test to fail on windows ruby 2.0 x86

Ruby 2.0 x86 on windows does not observe the 'TZ' environment variable, so the
test would generate a Time object whose `#zone` was 'Eur', but had timezone
offset based on the current timezone.

    C:\work\puppet>ruby --version
    ruby 2.0.0p481 (2014-05-08) [i386-mingw32]
    C:\work\puppet>irb
    irb(main):001:0> ENV['TZ'] = 'Europe/London'
    => "Europe/London"
    irb(main):002:0> tm = Time.local(2012, "dec", 11, 15, 59, 2)
    => 2012-12-11 15:59:02 -0800
    irb(main):003:0> tm.zone
    => "Eur"
    irb(main):004:0> tm.gmt_offset
    => -28800

Ironically, ruby 1.9 and 2.0 x64 do the correct thing:

    C:\Windows\system32>ruby --version
    ruby 2.0.0p481 (2014-05-08) [x64-mingw32]
    C:\Windows\system32>irb
    irb(main):001:0> ENV['TZ'] = 'Europe/London'
    => "Europe/London"
    irb(main):002:0> tm = Time.local(2012, "dec", 11, 15, 59, 2)
    => 2012-12-11 15:59:02 +0000
    irb(main):003:0> tm.gmt_offset
    => 0
    irb(main):004:0> tm.zone
    => "Eur"

This commit modifies the test so that we expect failure on windows 1.8 and
2.0 x86, otherwise, we expect the test to pass on other ruby platforms.

Reviewed-by: Josh Partlow <joshua.partlow@puppetlabs.com>
(maint) Namespace constant declaration in specs to prevent warnings

Add module namespacing to two specs declaring an FS constant (for
convenience) so that we don't receive warnings about the duplicate
declaration.