Expose psgi_app from the top-level:

Getting the PSGI app should not be done directly via Dancer::Runner
because that might change in the future. Although it is available
in the DSL, we still want to make this available through the top-level
without having to import the DSL.
Merge branch 'psgi-app-for-users'
Fix test in skeleton to use Plack::Test:

We have recently removed Dancer2::Test usage in favor of Plack::Test,
but we forgot that we deploy an example test, and that one still uses
Dancer2::Test. Fixed.
Merge branch 'plack-test-in-skeleton'
reflect changes
version bump
add timestamp
Merge branch 'release/0.143000'
Fix local link to jQuery and update jQuery to v1.11.1 (fixes GH #618)
Add Michał as a contributer and reflect changes.
Merge branch 'odyniec-master'
Make public_dir a lazy attribute

Using BUILD to populate an attribute in this was is not best practice.
Requied with a default, or lazy and provide a builder are obth better
solutions.

Go for the later, to allow the public_dir config to to altered up to
the point Handler::File is registered.
Only pass public_dir to Handler::File is using system paths

Allows the builder on the lazy public_dir to provide the appropriate value
Update hander_file tests to set public_dir via settings.

Closes #605
reflect changes
Merge branch 'bugfix/setting_public'
Allow Dispatcher to create a clean request by itself:

As part of untangling the Core::Context object, we first allow the
Dispatcher class to create its own request inside the dispatching
process.

It does this for each app, in the loop, because the request is
dependent on the app. Creating the app is measured to be a very
cheap operation.

The other way would be to make the "app" attribute in the request
class a read-write, and then set it, which we prefer not to do. Or,
alternatively, we could keep the app alive all the time and pass it
as a parameter between all functions. Eww.
Start peeling away the $context->request references:

One of the first steps to tearing out the context variable in the
dispatcher is to remove any context request objects, and making it
use our new $clean_request (which will, obviously, be renamed to
$request later).
Replace the request in Context with our new clean request:

Next step: we replace the request Core::Context uses with the request
we created ourselves.

A major problem is that Core::App sets up engines according to that
context, and attributes like "is_behind_proxy" get initialized by
that. This is done in a trigger for the "context" attribute in
Core::App.

We move this to a method that we can then manually call, which will
later be removed when we remove Core::Context.
Removing last usage of the original request in the dispatcher:

There is one more instance in which it's used, and that has easily
been replaced without any problem.