(TK-37) Bump default request buffer size

Bump the default size of the request header buffer to 8192 as
per TK-37. Also, bump the size of the request header size to
16192, as having cookies over a certain size would cause the
request to fail with a 413 error regardless of how high the
requestHeaderBuffer was set.
Make request header size configurable

Add a new configuration option, :request-size, to the webserver
configuration. This will allow the user to increase the size
of the request header when they are sending an extremely
large cookie as part of a request, as if this is too
small, an HTTP 413 error will be returned. This should not need
to be increased except in cases with unusually large headers.
Remove large-cookie

Remove large-cookie from common.clj, as it was no longer
being used.
(TK-37) Cleanup based on PR comments

Cleanup code based on comments received on the PR. Use default
variables instead of hardcoded numbers for the requestBufferSize
and requestHeaderSize. Change the name of the key to configure
the request header size. Cleanup config tests by adding the
default request header size within expected-http-config?
and expected-https-config?. Ensure Jetty does not truncate
large header.
(TK-37) Update docs to reflect new option

Update docs to reflect the new option to configure the maximum
request header size.
Merge pull request #43 from fpringvaldsen/TK-37

(TK-37) Increase default request buffer size and make request header size configurable
(TK-23) Update to clj-http-client 0.2.1

This commit updates jetty9 to the latest clj-http-client release,
and in the process, fixes some transient test failures having
to do with a race condition.  (SSL-related tests that were intended
to cause exceptions could end up with one of two different exceptions
when we use an asynchronous HTTP client.)

Conflicts:
	test/clj/puppetlabs/trapperkeeper/services/webserver/jetty9_service_proxy_test.clj
(TK-23) Get rid of unnecessary calls to `true?`
Merge pull request #48 from cprice404/bug/master/TK-23-update-to-http-client-0.2

(TK-23) Update to clj-http-client 0.2.0
Update CHANGELOG for 0.6.1 release
Merge pull request #51 from cprice404/maint/master/CHANGELOG-for-0.6.1

Update CHANGELOG for 0.6.1 release
lein-release plugin: preparing 0.6.1 release
lein-release plugin: bumped version from 0.6.1 to 0.6.2-SNAPSHOT for next development cycle
TK-48 ambigous slash when building proxy URL

This patch allows me to create clean URLs when using TK proxy which are accepted by our pe-activity service.

I cannot tell whether this is correct solution, it's just a proposal. I don't think there is a way to get rid of the ambigous slash without patching TK.