confirm oxide to rancher machine states are correct

[briandowns]

Audit the toRancherMachineState function to ensure Oxide instance states are mapped to the semantically correct Rancher machine states. For example, should oxide.InstanceStateRebooting map to state.Stopping or state.Starting? What's the behavior difference between Rancher machine states?

rancher-machine-driver-oxide/oxide.go

Lines 563 to 580 in 8e3b6df

	// toRancherMachineState converts an Oxide instance state to a Rancher machine
	// state.
	func toRancherMachineState(instanceState oxide.InstanceState) state.State {
	switch instanceState {
	case oxide.InstanceStateCreating, oxide.InstanceStateStarting:
	return state.Starting
	case oxide.InstanceStateRunning, oxide.InstanceStateMigrating:
	return state.Running
	case oxide.InstanceStateStopping, oxide.InstanceStateRebooting:
	return state.Stopping
	case oxide.InstanceStateStopped, oxide.InstanceStateRepairing:
	return state.Stopped
	case oxide.InstanceStateFailed, oxide.InstanceStateDestroyed:
	return state.Error
	default:
	return state.None
	}
	}