MMCore: Enforce pre/post initialization rules

[marktsuchida]

• Most non-property operations require an initialized device
• Pre-init properties must not be set after initialization
• Device initialiation may only be attempted once per device instance

These rules have been unstated previously, but had to be observed. Now make it an error (throw a CMMError).

All CMMCore member functions that do not throw CMMError were reviewed to make sure newly-thrown exceptions are not left uncaught in SWIG wrappers.

MMCore version bumped 10.4.0 -> 10.5.0.

Closes #366.

Cc: @tlambert03

[tlambert03]

I like it!!

What are your thoughts on adding an isInitialized(label) method? I see that with the current structure, it doesn't really matter, since requireInitialized errors are all being caught by core calls and dropped... but it would allow "look-before-you-leap" style approaches too. Unless there's a specific aversion to giving a public accessor to that data?

[marktsuchida]

No reason to hide it, but it's a little tricky, because devices are actually in one of 3 states:

• uninitialized (initializeDevice() never called since loading)
• initialized (successfully on first try)
• initialization failed (device cannot be reused without unloading/loading)

Presumably isDeviceInitialized() would return true only for the second state, but then a false return value would not indicate "can initialize". I suppose we could have a function returning an enum with these 3 states.

(Technically there is also a "shut down" state, but (thankfully) this is not observable outside of MMCore.)

[tlambert03]

I think the enum response would be great (similar to deviceDetectionStatus). Informative, extensible...