add new dapl MIC provider (MCM) to support MIC RDMA proxy services

add new dapl MIC provider (MCM) to support MIC RDMA proxy services

Provider supports all modes of connectivity and will setup data paths
based on endpoint locality and platform constraints. Provides
transparent DAT API support for RDMA writes, RDMA write with
immediate data, Sends, and Recvs. No RDMA read or atomic support.
To use MCM provider an application can use the new ofa-v2-mcm
device definations in dat.conf. Intel MPSS is required for
for MCM provider build and usage.

The following shows connectivity modes and data paths:

HST -> HST to HCA
MSS -> MIC to HCA same socket
MXS -> MIC to HCA cross socket

1.  HST->HST:    Xeon->HCA->fabric->HCA->Xeon  (direct->direct)
    HST<-HST:    Xeon<-HCA<-fabric<-HCA<-Xeon  (direct<-direct)

2.  MSS->MSS:    KNC->Xeon->HCA->fabric->HCA->KNC  (proxy->direct)
    MSS<-MSS:    KNC<-HCA<-fabric<-HCA<-Xeon<-KNC  (direct<-proxy)

3.  MSX->MSX:    KNC->Xeon->HCA->fabric->HCA->Xeon->KNC  (proxy->proxy)
    MSX<-MSX:    KNC<-Xeon<-HCA<-fabric<-HCA<-Xeon<-KNC  (proxy<-proxy)

4.  MSS->MSX:    KNC->Xeon->HCA->fabric->HCA->Xeon->KNC  (proxy->proxy)
    MSS<-MXS:    KNC<-HCA<-fabric<-HCA<-Xeon<-KNC        (direct<-proxy)

5.  MSS->HST:    KNC->Xeon->HCA->fabric->HCA->Xeon  (proxy->direct)
    MSS<-HST:    KNC<-HCA<-fabric<-HCA<-Xeon        (direct<-direct)

6.  MSX->HST:    KNC->Xeon->HCA->fabric->HCA->Xeon  (proxy->direct)
    MSX<-HST:    KNC<-Xeon<-HCA<-fabric<-HCA<-Xeon  (proxy<-direct)

Signed-off-by: Arlin Davis <arlin.r.davis@intel.com>