InstanceChangeProvider: view_no='lastSentPrePrepare' must be of int type

v1.8.0-11-g1895044

warning in logs:

```
$ RUST_LOG=warn LOG_LEVEL=warn ./manage start
$ ./manage logs
node3-1 | start_indy_node Node3 0.0.0.0 9705 0.0.0.0 9706
node1-1 | start_indy_node Node1 0.0.0.0 9701 0.0.0.0 9702
node1-1 | 2024-08-14 19:21:51,920|WARNING|instance_change_provider.py|InstanceChangeProvider: view_no='lastSentPrePrepare' must be of int type
node2-1 | start_indy_node Node2 0.0.0.0 9703 0.0.0.0 9704
node4-1 | start_indy_node Node4 0.0.0.0 9707 0.0.0.0 9708
node4-1 | 2024-08-14 19:21:52,953|WARNING|instance_change_provider.py|InstanceChangeProvider: view_no='lastSentPrePrepare' must be of int type
node2-1 | 2024-08-14 19:21:53,036|WARNING|instance_change_provider.py|InstanceChangeProvider: view_no='lastSentPrePrepare' must be of int type
node3-1 | 2024-08-14 19:21:53,099|WARNING|instance_change_provider.py|InstanceChangeProvider: view_no='lastSentPrePrepare' must be of int type
```

Start by reproducing the warning with `./manage start` and `./manage logs`, then inspect `instance_change_provider.py` where the message is emitted. Trace why `view_no` is set to the string `lastSentPrePrepare`; done means startup no longer reports this type warning and the value is handled as an integer.

Written by the indexing model from the issue text.