goodbye async-http-client

it's useless.  it's worse than useless, it's broken.
upgrading to netty 5

tons of interface changes! and it's still in alpha so maybe more.  but!
it also has an async dns resolver which i need
testing a thing that has been wanting it

i left the warning in place forever ago.  finally just took care of it
killing a warning

clearly i have no plans for this field, so it is gone.  byebye!
make sure the repl test doesn't depend on external dns being available

and other cleanup.  wheee
the new http client

or at least a beginning
looking for netty leaks
creating hashcodes of configuration objects

this behaves as a shortcut equality check that can be saved. it's
possible to have collisions but that shouldn't be a problem generally
speaking and if it becomes so, then we can serialize some other way
configuration objects should all have hashCodes

WELL OKAY THEN.  HAVE EM
http server refactor

this is a bit of a detour.  i will finish it next feature. really just
testing out that the restartability idea is correct
small improvement to the config hashCode

testing it to verify it suits the purpose, and eliminating the tiny
chance of generating a pathological base number
configuration errors are now collected

here's the facility.  next step is to spread it everywhere
config system updated

this is a partial update, cleaning up the support. there is also the
start of a change to error reporting, to allow picking up as much as
possible.  that, i might just undo right now haha
locking down the configuration api
adding location information to config errors

some validation functions still need to have depth information added but
the basic mechanism works
missing commits
the basics of the new HTTP client

- two classes make up the API, HttpRequester and HttpResponseListener
- the integration test is extremely basic right now but so is the entire
facility.
- needs more unit tests
leaving a note
test improvement
added in http decompression + test refinement