Bug: Session state in database does not change after a reconnect

[VeroSec]

We have noticed that after an ECU reconnect, the logged status of the scanned session in the database is not updated according to the current session.

[rumpelsepp]

@fkglr You might know where this could be fixed quickly? I think it is a oneline update_state() kind of thing?

[VeroSec]

The possibilities we have, to log the right session in the database, are:

1. Force to set session after reconnect() in the scanner code. (this is our current workaround)
2. Add read_session() to the code in ecu.reconnect() to avoid the bug for future scanners.