Add more member/free/both macros to cover more use cases

From pipable_algorithms.cpp:
// This is a bit loose, because it allows us to write "sort(v) |
// unique(u)" or similar. It works fine for this example, but in
// production code you may want to write out the three member functions
// generated by this macro, and add SFINAE or concepts constraints on what
// is accepted on the right.
BOOST_YAP_USER_BINARY_OPERATOR_MEMBER(bitwise_or, ::algorithm_expr)

We really should have another macro that has a place for a trait-based constraint here. Looking at the other macros in the full list in the docs, it seems like there's a lot of room for a lot more macros here.