tests/{client,server}: Assert context and connection values in send/recv/accept/connect events

tcp/sock/eth/verbs look OK.
cci.h: document that rma handle flags are ignored when used as a local handle
cci.h: clarify that the RMA FENCE is per connection
API: remove the endpoint context

Based on Scott's email:
 During the call Friday, Patrick asked if the endpoint context was needed.
 I argued that we could have as many as one endpoint per device or one
 endpoint per core.
 Upon further reflection, I agree with Patrick. We need user supplied
 contexts for connections, MSGs, and RMAs, because these are asynchronous
 operations. We need them to determine the owning connection, etc., when
 an event is returned from get_event().
 With endpoints, however, there is no call that returns something and we
 do not know the owning endpoint. For example, get_event() is per endpoint
 and the endpoint is a parameter to the call.
 Given this, I recommend just dropping the void *context from cci_endpoint_t.
Merge pull request #26 from CCI/topic/no-endpoint-context

API: remove the endpoint context
tcp: don't corrupt the closing conn list

Queue once. Don't requeue the same conn twice.
tcp: do not try to send on a closing connection

Simply queue the failed send on ep->evts with the event status
of CCI_ERR_DISCONNECTED.

Also, move conn status changes to under the ep->lock just before
moving to the new queue.
sock: Modify the allocation of RX/TX buffers based on feedback and patch from
G. Bosilca.
Merge branch 'master' into gvallee/sock