feat: add a console warning if writing to cookies doesn't work

Summary of change

add a console warning if writing to cookies doesn't work

We check when saving the last access token update time
We only check once per reload (store the result in memory)
The warning is repeated on every access token update to increase the chances of devs noticing it.

Added a new test that checks that this is logged

N/A

[x] Changelog has been updated
[ ] frontendDriverInterfaceSupported.json file has been updated (if needed)
- Along with the associated array in lib/ts/version.ts
[x] Changes to the version if needed
- In package.json
- In package-lock.json
- In lib/ts/version.ts
[x] Had run npm run build-pretty
[x] Had installed and ran the pre-commit hook
[x] Issue this PR against the latest non released version branch.
- To know which one it is, run find the latest released tag (git tag) in the format vX.Y.Z, and then find the latest branch (git branch --all) whose X.Y is greater than the latest released tag.
- If no such branch exists, then create one from the latest released branch.