provide bookletDbId (testId) when calling [PUT] `test/${testId}/log` correctly...

provide bookletDbId (testId) when calling [PUT] `test/${testId}/log` correctly even for BOOKLETLOADSTART
* it was not set in test-controller.service's this.bookletDbId, until bs.getBookletData is resolved (after reload for example)
* but call on [PUT] `test/${testId}/log` with BOOKLETLOADSTART was fired before
* in the old implementation bookletDbId was stored also (!) in the loginToken, so even if it was in fact provided via body of the call, tha backend knew the bookletDbId from the token and got it (only) from there.