Emulate a puppet Device-style class using a Resource API Transport. Can be
used to provide backwards compatibility like this:

```
require 'puppet/resource_api/transport/wrapper'
# force registering the transport
require 'puppet/transport/schema/panos'

module Puppet::Util::NetworkDevice::Panos
  class Device < Puppet::ResourceApi::Transport::Wrapper
    def initialize(url_or_config, _options = {})
      puts url_or_config.inspect
      super('panos', url_or_config)
    end
  end
end
```

(FM-7674) Add a Transport wrapper class

Neither the Device API, nor the wrapper need access to the config,
so we can immediately load the config, pass it on and never store it
ourselves here.

the JRuby 1.7 only implements ruby language 1.9 which chokes on the logging named arguments. Hiding the require as shown here will avoid the file being loaded for the server-side tests.

Loading a PuppetContext is not necessary on (the JRuby 1.7) puppet server, so stop trying to run the tests there.

This find other places where we need to handle passing a context

This uses the initial `list` implementation from the previous commit to access the schema
to create a context to pass around.

(FM-7691,FM-7696) refactoring definition handling in contexts

(FM-7690) Update transports cache to be grouped by environment

Using this accessor providers can talk directly to the transport
without having to go through the `Device` at all.

(FM-7726) implement `context.transport` to provide access

(FM-7726) cleanups for the transport

Transport support for device specific providers

This commit prevents validation from changing resource and connection_info  hashes passed into RSAPI from removing keys that are not in their schema.

(PDK-1271) Allow a transport to be wrapped and used like a device

Before passing the connection_info to the transport, wrap them in a PSensitiveType to prevent unexpected leaking of data.

(FM-7698) Ensure that sensitive values are handled correctly