Destroy/close functions should return void

[marktsuchida]

For example, OSc_Acquisition_Destroy().
Review other 'destroy' functions; it is preferable for these functions to never return an error, if possible.

[marktsuchida]

OSc_LSM_Destroy() can probably also be changed to return void, but we also need to clarify how to handle OSc_Device_Close(), which currently dissociates the device from the LSM, while OSc_LSM_Destroy() currently implies closing all its associated devices. This means that the LSM "owns" the opened-ness of the device(s), which is confusing because the LSM can have between 0 and 3 relationships to a given device.

Perhaps it will be simpler to require user code to always close a device when finished, making the relationship non-owning. Then, we need only define the behavior when an associated device is closed before the LSM is destroyed. In that case, all subsequent actions on the LSM (except for destroying it) could result in an error.

Additionally we should get rid of the OSc_LSM_SetClockDevice() and kin, instead requiring specifying all 3 devices upon creation (and, more importantly, prohibiting any change thereafter). (In this context, see also #8; this change will also help implement #2 by providing a single place to check compatibility between components.)

[marktsuchida]

First need to remove return value from the DeviceImpl Close() function. Also change device open/close so that it is independent of LSM association.