Add selection to chang IO-Link V1.0 / V1.1 - Problem with Application specific tag

The application specific tag can cause problems in some old systems when an older device is replaced with a newer one (from FW V2.2.0 - SN 20340001).
If the sensor is only assigned via the VendorID and DeviceID in the IO-Link master (and not with the correct IODD), our device does not know whether it should communicate with IO-Link V1.0 or IO-Link V1.1.
Since we have to stay in the specification, our sensor starts with IO-Link V1.1. If the master also supports IO-Link V1.1, the sensor remains an IO-Link V1.1 device.
The application specific tag was shortened in the standardization from 64 bytes for IO-Link V1.0 to 32 bytes for IO-Link V1.1. We have handled this as well as possible in the device, but errors can still occur under certain circumstances.

In order to correct these issues, the sensor can be manually set to IO-Link V1.0 from FW V2.2.2 (SN 21130924) onwards via SOPAS ET (this setting remains even after a reset).