When the Enqueue method was removed in favor of the Order/Configure
methods, the existing Broadcast code continued to use them very much
like the old Enqueue method.

This CR removes the hack which allowed the Broadcast code to continue to
function and instead leverages the msgprocessor code to appropriately
route messages to either Order or Configure.

Because the filters were removed from the blockcutter, the only place
they are currently used is in the Broadcast path.  This injects an
unneeded dependency into the Broadcast framework, making tests more
difficult to mock, and generally complicating the code.

This CR removes the filtering from the Broadcast path, in favor of doing
the filtering entirely in the msgprocessor path.  This was at one point
split into two CRs around issue FAB-5268, but it turned out to be
infeasible to break this into two changes while not breaking the e2e.

Change-Id: I6ef3595f26a4e9dfdbf6dec636b434e725ccd6f2
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>