(PUP-2303) Fix arguments of ArgumentError

Yo dawg, I heard you like ArgumentErrors so I put an
ArgumentError in your ArgumentError.

This makes errors in fileserver config much more readable and
easier to find.
(PUP-1597) Fix contain functions lookup of class with leading ::

When the contain function creates edges it looked up resources
without removing the leading :: in the name. The catalog never stores
these, and thus an edge was formed between a resource and nil.

This commit simply removes the ::. There is no checking that a resource
is actually returned since they should all be there due to the call to
include them in the catalog (which would fail if it was not possible to
include them).

A test is also added for the erronous (and now fixed case).
(PUP-2214) Change doc application to use current environment
(PUP-2214) Change parser application to use current_environment

This changes the parser face to use the current_environment instead
of looking up the "configured environment" from settings and then
using that environment.

This also adjust the documentation for the command wrt. use
with --parser future.
(PUP-2214) Change node/clean face to use configured environment
(PUP-2214) Fix failing doc tests

Doc tests with mocking did not work, needed to use a real configured
env.
(PUP-2214) Add comment that node.environment is source of environment

This note is to ensure the lookup of :environment is not changed
to a lookup of :current_environment, since the node's environment
is what is used to determine what the current_environment should be.
(PUP-2014) Make module use current_environment

Module now uses current environment instead of configured
environment when being asked for a module and not supplying
an explicit environment name. It used to lookup to configured
environment giving invoking logic no chance to modify the
default without modifying the setting.
(PUP-2214) Make util rdoc and related parser use :current_environment
(PUP-2214) Add comment about looking up environment for requests.
(PUP-2214) Change autoloader to use current_environment for changed?

This changes the autoloader to use the current_environment as the
environment when performing a changed? operation. (It used to check
if the configured environment was changed).

The complicated bootstrap support still uses lookup of configured
environment as that is the fallback when booting.
(PUP-2214) Add comment what command_line "current_environment" means
(PUP-2214) Add comment about application's use of configured env
(PUP-2214) Add comment about module_tool's lookup of requested env
(PUP-1597) Handle containment of relative names

The contain() function made an error when dealing with a relative name.
It assumed that the class that was actually included was always the same
as the name that it was given. In many cases this is true, but when the
name is found via a relative lookup (e.g. contain(bar) inside a class
foo, when a foo::bar exists), the assumption breaks down. The source of
the problem is that it tries to look up the included class after the
fact. Without all of the extra information about namespaces it isn't
able to find the right class.

To fix this, the include() function has been updated to return the
class resources that it included (including those that were already
present). This allows the contain() function to create the appriate
edges with the exact resources needed.

A secondary change in this was to remove the checks for include not
being able to include a class. The compiler method that is involved
already makes that check and raises an error, so the include functions
code was simply redundant.
(PUP-1597) Separate different modes of including

The evaluate_classes method has a couple different responsibilities and
inputs. This is just an attempt to pull them apart some and make the
flows a little more straightforward.
(maint) Update beaker to 1.11.0

With beaker 1.10.0 (and probably any earlier version that included the
dependency on google-api-client), we started seeing this error:

/usr/local/opt/rbenv/versions/2.1.0/lib/ruby/gems/2.1.0/gems/bundler-1.5.2/lib/bundler/rubygems_integration.rb:250:in `block in replace_gem': can't activate jwt (~> 0.1.4), already activated jwt-1.0.0.

This issue is discussed in https://tickets.puppetlabs.com/browse/QENG-655,
and it appears to be addressed by beaker 1.11.0.
Merge branch 'stable'
(maint) Reduce resource lookup

scope.resource was called multiple times. Even if this is a simple
method, it is still a method call and is slower than just holding onto
the result. This also removes some comments that appear to be out of
date.
(PUP-1028) Specify various ways of matching nodes

There were no tests that tried to specify how node statements are
selected. This adds coverage for various ways in which a node statements
can match a given node object and varifies that the future evaluator and
the current evaluator produce the same results.

There are 2 cases where the future evaluator isn't able to handle the
same node statements: using numbers. One case, where a name begins with
a number, seems completely reasonable. The other case, where the name is
a valid number, seems like an arbitrary restriction and so we need to
discuss.