erp5_oauth2_authorisation: Do not edit OAuth2 Session on every refresh token issuance

Malevolent users may decide to only - and repeatedly - present an otherwise
valid refresh token, causing the issuance of a new access tokens everytime,
likely along with new refresh tokens, causing many ZODB writes.
Avoid this by pushing the token expiration date by one lifespan accuracy,
so there can only be one write per session per lifespan accuracy period.
20 jobs for for_testrunner_1 in 0 seconds
latest
Status Job ID Name Coverage
  External
passed ERP5.CodingStyleTest-Master

03:33:53

passed ERP5.CodingStyleTest-TestRunner1

01:47:00

failed ERP5.PerformanceTest-Master

00:35:46

failed ERP5.PerformanceTest-TestRunner1

00:35:16

failed ERP5.UnitTest-Master

04:51:59

passed ERP5.UnitTest-TestRunner1

04:03:29

passed SlapOS.Eggs.UnitTest-Master.Python2

00:32:29

passed SlapOS.Eggs.UnitTest-Master.Python3

00:30:23

passed Wendelin.UnitTest-Master

00:44:19

passed ERP5.PerformanceTest-Master

00:35:21

failed ERP5.UnitTest-TestRunner1

05:31:41

passed ERP5.UnitTest-TestRunner1

03:01:09

passed ERP5.UnitTest-TestRunner1

11:00:01

passed SlapOS.Eggs.UnitTest-Master.Python2

00:24:23

passed SlapOS.Eggs.UnitTest-Master.Python2

00:23:15

passed SlapOS.Eggs.UnitTest-Master.Python3

00:26:00

passed SlapOS.Eggs.UnitTest-Master.Python3

00:26:52

passed SlapOS.Eggs.UnitTest-Master.Python3

00:26:24

passed SlapOS.Eggs.UnitTest-Master.Python3

00:28:43

passed Wendelin.UnitTest-Master

01:10:36