Force all

@agorrod Please review this.  It contains moving the one line for the aggressive we talked about last night.  I added the LSM table name to a bunch of verbose output.  I added a loop in flush so that when we force a flush we make sure to flush all chunks.  I think this will make the medium-compact run consistently better performance.

The code is still doing unexpected things in medium-lsm-multi that impact performance.  The compacts do not fully merge with multiple tables and I haven't yet figured out why.
@sueloverso This change makes me nervous. It means that a worker thread that is shared across all LSM trees will just continue flushing all chunks from a single tree. That's likely to cause starvation for other trees.

I've been thinking about this a bit, and I think maybe what we really need here is for the current "switch" queue to hold both switch and flush operations.