Better error messages during calendar connection

[davinotdavid]

Description of the Change

We are currently capturing some errors during calendar connection:

CalDAV

- GoogleCaldavNotSupported
  - "Google CalDAV is not supported. Please use the 'Connect Google Calendar' option"
- RemoteCalendarConnectionError (no auth support)
  - "We couldn't connect to your calendar. The server does not support any of the available authentication methods."
- RemoteCalendarConnectionError (no CalDAV)
  - "We couldn't connect to your calendar. The remote calendar does not support CalDAV."
- RemoteCalendarConnectionError (unauthorized)
  - "We couldn't connect to your calendar. Please check your username and password, then try again."
- TestConnectionFailed
  - Custom reason passed through, depends on reason.

Google

- access_denied / google-connect-to-continue
  - "You must connect at least one Google account to continue."
- GoogleScopeChanged / google-scope-changed
  - "You must enable Calendar and Event access to use Thunderbird Appointment."
- GoogleInvalidCredentials / google-invalid-creds
  - "Google authentication credentials are not valid."
- State mismatch/ google-auth-fail
  - "Google authentication failed."
- Sync failure / google-sync-fail
  - "An error occurred while syncing calendars. Please try again later."

However, we were only showing the title "We couldn't connect to your calendar" and not the description. Now we are showing that in the notice bar!

Also, we are now separating a little bit the NotFoundError and an invalid XML returned as their own error messages.

Screenshots of some examples:

Known issues / Things to improve

• Our NoticeBar component could use some style changes for title / description as there's not a lot of hierarchy in typography.

Benefits

• Better / more actionable error messages during calendar connection

Applicable Issues

Fixes #1457

[devmount]

This is great Davi, thank you! Just a language nit below.

This might be also related to #1419, right?

[davinotdavid]

@devmount yes! Related with #1419 but not fixing that just yet as this PR is only for the FTUE and the one in the issue is about the BookersPage (although it might be easier now to catch the exception on our end and show an error).