libfabric-2.0: separate FI_DIRECTED_RECV capability for message and tagged message

[j-xiong]

Define new bits that only applies to message or tagged message. The original cap covers both.

[j-xiong]

The purpose is to allow transport to support only one of them due to hardware limitation.

[raffenet]

MPICH only utilizes this capability for tagged messages, so splitting it should be no issue for us.

[swelch]

It also allows enables full non-matching interface performance with FI_MSG (no initiator matching) while maintaining full matching for FI_TAGGED (tag and initiator) even if hardware supports it for both. Seems particularly useful in the above use case where FI_DIRECTED_RECV is only used on FI_TAGGED.

[j-xiong]

The proposal is to add FI_DIRECTED_TRECV cap bit.

[j-xiong]

See #10317

[j-xiong]

Done.