#944: Fixed auth. sessions not persistent

[davegarthsimpson]

Motivation

To ensure login sessions to Arduino Cloud are persistent when closing and reopening the application.

Issue

We were initialising our backend auth service and performing token refreshes without the required "authOptions" properties. These properties are set on the frontend after the backend service is initialised.

Change description

We now perform the auth service initialisation and token refreshes on the frontend after the required "authOptions" properties are set.

Removed initialisation from the backend service;
Created a method on the backend service to initialise the auth service from the frontend (and added the method to the related interface);
Created an "initialised" variable in the backend auth service to ensure initialisation does not run more than once (incase of multiple frontend instances);
Invoked initialisation on the frontend service after setting required "authOptions" properties;

Reviewer checklist

• PR addresses a single concern.
• The PR has no duplicates (please search among the Pull Requests before creating one)
• PR title and description are properly filled.
• Docs have been added / updated (for bug fixes / features)

[CLAassistant]

All committers have signed the CLA.

[ubidefeo]

Works as expected
LGTM

[kittaakos]

Note, above this initAuthSession call, the setOptions is a void, hence notification. It's a "fire and forget" event, so by the time you call initAutSession it is not ensured that the options were set or arrived at all.

In the long run, we have to change all similar calls from foo(arg: any): void to foo(arg: any): Promise<void>, and change the code from this

this.setOptions();
this.service.initAuthSession()

to this:

await this.setOptions();
this.service.initAuthSession()

//CC @fstasi, @AlbyIanna, @davegarthsimpson, and @francescospissu