First steps towards the SAS partnership
* otp flow now pretends to do the linking
* Update LinkAccountForm header
* Update redirect times
* Clean up comments
* Set maxAge on sas cookies
* make all SAS routes protected
* Merge remote-tracking branch 'refs/remotes/origin/feature/sas-login' into feature/sas-login
* Require auth for sas link flow
* Fix resend otp
* Add error support to OneTimePasswordForm
* Add Sentry to SAS error boundary
* Move SAS_REQUEST_OTP_STATE_STORAGE_COOKIE_NAME
* Add missing translations
* Merge branch 'master' of bitbucket.org:scandic-swap/web into feature/sas-login
* Merge branch 'feature/sas-login' of bitbucket.org:scandic-swap/web into feature/sas-login
* Add TooManyCodesError component
* Refactor GenericError to support new errors
* Add FailedAttemptsError
* remove removed component <VWOScript/>
* Merge branch 'feature/sas-login' of bitbucket.org:scandic-swap/web into feature/sas-login
* remove local cookie-bot reference
* Fix sas campaign logo scaling
* feature toggle the SAS stuff
* Merge branch 'feature/sas-login' of bitbucket.org:scandic-swap/web into feature/sas-login
* fix: use env vars for SAS endpoints
Approved-by: Linus Flood
This implements the actual call to the API to create a booking. That’s the only thing it does, it doesn’t handle the response in any way.
This PR is just to get it there and the new booking sub team will handle it further, with payment etc.
Approved-by: Michael Zetterberg
Approved-by: Fredrik Thorsson
Approved-by: Simon.Emanuelsson
