mb2hal: fix pin type change for version 1.000

[sensille]

followup to #2299 against 2.9, @hansu @petterreinholdtsen

[hansu]

I added a test for that in #2274
It shows really good the failure in current 2.9 without this patch:

Running test: ../tests/mb2hal/mb2hal.2
--- ../tests/mb2hal/mb2hal.2/expected   2023-01-15 14:53:00.838001000 +0100
+++ ../tests/mb2hal/mb2hal.2/result     2023-01-15 14:57:49.774001000 +0100
@@ -18,10 +18,10 @@
 
 Component Pins:
 Owner   Type  Dir         Value  Name
-     4  float IN              0  mb2hal.Modbus_fnct_06.00
-     4  float IN              0  mb2hal.Modbus_fnct_06.01
-     4  float IN              0  mb2hal.Modbus_fnct_06.02
-     4  float IN              0  mb2hal.Modbus_fnct_06.03
+     4  s32   IN              0  mb2hal.Modbus_fnct_06.00
+     4  s32   IN              0  mb2hal.Modbus_fnct_06.01
+     4  s32   IN              0  mb2hal.Modbus_fnct_06.02
+     4  s32   IN              0  mb2hal.Modbus_fnct_06.03
 
 Component Pins:
 Owner   Type  Dir         Value  Name
@@ -32,8 +32,8 @@
 
 Component Pins:
 Owner   Type  Dir         Value  Name
-     4  float IN              0  mb2hal.Modbus_fnct_16.00
-     4  float IN              0  mb2hal.Modbus_fnct_16.01
-     4  float IN              0  mb2hal.Modbus_fnct_16.02
-     4  float IN              0  mb2hal.Modbus_fnct_16.03
+     4  s32   IN              0  mb2hal.Modbus_fnct_16.00
+     4  s32   IN              0  mb2hal.Modbus_fnct_16.01
+     4  s32   IN              0  mb2hal.Modbus_fnct_16.02
+     4  s32   IN              0  mb2hal.Modbus_fnct_16.03
 
*** ../tests/mb2hal/mb2hal.2: XFAIL: result differed from expected

[hansu]

Thank you!