Improve parameter validation

[epage]

At least some of the write flavors don't validate their input

• Unsupported frames are silently dropped
• Wrong number of frames or signals might error or might silently corrupt the data

Areas impact:

• nixnet.convert
• nixnet._session.signals
• `nixnet._session.frames

Suggestion: where possible, add a "verify=Trueparameter towrite` functions. When enabled, it will perform checks to make sure the parameters are correct if the driver won't do them itself. Its optional to allow performance critical applications to remove these checks from their inner loop

Unsupported frames: unsolved

Inspiration: nidaqmx's Writer.verify_array_shape.

How this breaks compatibility: If an invalid array was being passed in, the application will now error instead of silently fail. Should not impact most users.

[epage]

• OutFrames.write
  • For stream and queued modes, session.frames is ignored.
• SinglePointOutFrames.write
  • Expectation: len(frames_param) must match len(session.frames) (see help)
• SinglePointOutSignals.write
  • Expectation: len(signals_param) must match len(session.signals)
• XYSignals.write (future)
• WaveformSignals.write (future)
• SignalConversionSinglePointSession.convert_frames_to_signals
• SignalConversionSinglePointSession.convert_signals_to_frames
  • Expectation: len(signals_param) must match len(converter.signals)
  • On failure: Extra signals ignored, too few causes API to hang for some reason instead of throwing about too few signals