merge last_activity and last_check updates

[icewind1991]

updateActivity has been updated to also write any other changed field.

the debounce for updating last_activity is changed so it always updates if another field of the token has been updated, this ensures that last_check if updated even if last_activity is still in the debounce period.

This is pretty much a 2nd version of #1037, which was reverted(#29682) after the last_activity updating changed by #29357

[icewind1991]

I've done some basic testing to ensure that both last_activity and last_check get updated under normal use

[come-nc]

I do not have enought understanding/knowledge to approve this, sorry

[susnux]

Looks good from my understanding, very clean!

[susnux]

But the test needs to be adjusted @icewind1991

 There was 1 failure:

1) Test\User\SessionTest::testLoginLastCheckUpdate
Expectation failed for method name is "updateToken" when invoked 1 time(s).
Method was expected to be called 1 times, actually called 0 times.

[ChristophWurst]

Wasn't this addressed with #45026?