Rename StrategyAt.* -> Strategy.*Response.

Addendum to 64feeee.
Merge pull request #429 from benma/atResponse

Rename StrategyAt.* -> Strategy.*Response.
OTStorage: remove out-commented code
OTStorage: inline DECLARE_PACKED_BUFFER_SUBCLASS macro
Merge pull request #425 from toxeus/inlineMacro

OTStorage: inline DECLARE_PACKED_BUFFER_SUBCLASS macro
Fix one missing conversion from @msg to msgResponse.
Merge pull request #433 from benma/atResponse

Fix one missing conversion from @msg to msgResponse.
ChangeLog: update to version 0.94.0
Merge pull request #418 from toxeus/changelog

ChangeLog: update to version 0.94.0
Removed commented out stuff and unnecessary comments.
Reordered members for clarity.
Cleanup of init of Client and passing arguments.
Removed is-running-as-script for client.
Moved member variables last.
Moved ctor and dtor first.
Hold socket in smart pointer.
Merge pull request #431 from murrekatt/transport_cleanup

Transport cleanup
Notary: send empty response on error

(Continuation of #426)

Currently, sending an invalid message causes the Notary to hang indefinitely
because ZeroMQ waits for a Send() call.

According to the name of the return value of `processMessage`, the Notary should
"disconnect" a client that sends an invalid request. However, ZMQ_REP is not
designed to be used that way:

> A socket of type ZMQ_REP is used by a service to receive requests from and
> send replies to a client. This socket type allows only an alternating sequence
> of zmq_recv(request) and subsequent zmq_send(reply) calls.

http://api.zeromq.org/3-2:zmq-socket

There may be a some way to disconnect a client that sends an message, but for
now, I think it is okay to just send an empty response for invalid requests.

Other changes:

* Log all messages
* Allow OTSocket_ZMQ_4 to send empty responses.