Udsoncan

**Improvements**
- Various improvement in J2534 module (credit kirya-dev ). See 248
- Made Close device after Discconnect. Previously, cant reconnect to the device (ERR_DEVICE_IN_USE).
- Avoid debug log after error log.
- Raising abnormal exception around connection to the J2534 device.
- Fix error J2534 Error: CAN_ID_BOTH and CAN_29BIT_ID are the only valid ConnectFlags according J2534 standard.
- Fix error Parameter pInput must be NULL.
- Add read_vbatt for j2534 connection
- Avoid extra access to DLL (log_last_operation)
- Fix PassThruStartMsgFilter for any interfaces according standard (Sets 0xCCCC_CCCC as a stub. Devices like OpenPoprt and Pulsar are not receiving messages correctly)

- Bug fix
- Adjusted `SecurityAccess.request_seed` minimal level to 1 as per ISO-14229. Fixes 220

- Improvements
- Added py.typed marker
- Less confusing error message when a timeout occurs following NRC 0x78

**New feature**
- CommunicationControl now supports ``nodeIdentificationNumber`` parameter introduced in the 2013 version of the standard. Fixes 216

**Changes**
- Updated example on index page to match changes introduced in 1.21

**Bugfix**
- 207 : Fixed broken compatibility with Python 3.7

**New features**
- Added the ``client.test_data_identifier()`` method

**Bugfix**
- Closing ``SocketConnection`` and ``IsoTPSocketConnection`` does not hang when provided with a socket in blocking mode (191)
- Fixed performance degradation introduced in v1.21 when requesting DIDs with a large configuration (185)

**Bugfix**
- Fix 199 : IsotpSocketConnection does not support ``can-isotp`` v2

**Breaking Changes!**
- ``IsotpSocketConnection`` requires an ``isotp.Address`` object and will not accept ``txid`` and ``rxid`` like before. This interface change could hardly be avoided while keeping the code sane.