Automatically clear circular buffer in continuous sequence acquisition

[henrypinkard]

This adds an overwrite mode to the circular buffer, which means that when an image is inserted and there's no more space, it will automatically clear itself. Currently, most cameras do this manually when there is an error on insert.

This is motivated by the need to deprecate the ability of devices to clear and allocate the buffer in the core. This should instead be done by higher level application code.

One thing I don't fully understand is the stopOnOverflow argument of startSequenceAcquisition. Some, but not all, cameras appear to have logic that changes behavior based on this flag, but I'm not aware of any higher level code that ever sets this to false when running a finite sequence of N frames.

Regardless, stopOnOverflow shouldn't be an issue for merging this, because the only time we set overwrite=true is when calling startContinuousSequenceAcquisition, where stopOnOverflow is always false

[marktsuchida]

Thanks, @henrypinkard. It's so much easier to confidently review a narrowly targeted PR like this!

[henrypinkard]

@marktsuchida ready to merge?

[marktsuchida]

Code-wise, this is ready to merge, but let's wait a bit for a day on which other major changes are not going into the nightly build (we upgraded to Java 11 today).

• Bump MMCore minor version
• Bump MMDevice interface version

The device interface version needs to be bumped, despite the apparent lack of change, because there is a behavioral change: camera adapters written assuming this change will fail Live when the buffer fills up if run with an older Core. We may want to coordinate this version increment with #640 and the actual removal of ClearImageBuffer().