asio-sys: handle asio messages

[JerwuQu]

Currently TODOs in code:

cpal/asio-sys/src/bindings/mod.rs

Lines 934 to 941 in 85fd82f

	Some(AsioMessageSelectors::kAsioResetRequest) => {
	// Defer the task and perform the reset of the driver during the next "safe" situation
	// You cannot reset the driver right now, as this code is called from the driver. Reset
	// the driver is done by completely destruct it. I.e. ASIOStop(), ASIODisposeBuffers(),
	// Destruction. Afterwards you initialize the driver again.
	// TODO: Handle this.
	1
	}

I'm not sure if the plan was to handle everything internally in cpal or to let the user listen for the messages for manual handling, but currently neither is supported.
The result is being unable to detect when a user changes audio settings in e.g. the ASIO4ALL GUI.

[roderickvd]

I'm thinking of two data points:

1. build_output_stream and build_input_stream take an error_callback that's passed to the user.
2. In CoreAudio, I believe that cpal handles changes to the default device by itself.