Update httpstats

What's Changed

• Adding deprecation notice by @gcase555 in #90
• Bump httpstats by @willyjfarrell in #91

Full Changelog: v1.10.0...v1.11.0

Fixes and dependency updates

What's Changed

• Update all dependencies by @renovate in #87
• Fix linter by removing broken dependency checker. We have Snyk for that
• Fix openapi files used for integration tests to match openapi schema

Full Changelog: v1.9.0...v1.10.0

validate ASAPTokenComponent TTL struct value

Validate ASAPTokenComponent TTL struct value is set greater than zero middleware creation. Prior to this release, the value was not validated, thus set to golang time.Duration zero value, effectively rendering every generated ASAP token with an already expired exp claims value.

add exponential backoff option to retry component

Adds the option to exponentially increase wait time during retries.

Fix Access Log Hogging the Response Body

The access log was wiping out the response body on an error response. This fixes that issue.

Fallback Principle Header Logging

Add ability to add fallback principle headers in cases where the previous in the list returns an empty value.

Upgrade Go and SDCLI

Upgraded Golang to version 1.17 and SDCLI to v1.2.3.

Log response body of status code greater than 399

Merge pull request #75 from asecurityteam/error-logging

Log response body excluding request with status code less than 400

Upgrade Go and Remove Vuln Libraries

An indirect dependency of ours gogo/protobuf has vulnerabilities, so we are removing the libraries bringing in that dependency as they are mostly irrelevant to our actual code compilation and pipeline and can be used locally by the user instead.

We also upgraded the Golang version to 1.16

Update to latest kin OpenAPI

The openapi library maintainer added a second option for a router that
is build on gorilla/mux. When they did this they re-arranged some of the
locations of types to offer a better abstraction over the router.
Additionally, they removed the term Swagger from all methods and types.

Generally, everything is still the same shape as before but the names
changed. The only part of this project that exposes the openapi library
types directly are the context methods in the clienttransport.go file.

Because these are exposed directly this is technically a breaking change
even though the new exposed types are identical to the old ones. The
only place within the project that these are used is the validation
middleware which worked without modifications.