Organization onboarding welcome message

[filiptronicek]

Description

Adds a customizable welcome message for organization newjoiners.

Related Issue(s)

Fixes CLC-1065

How to test

1. Sign up for https://ft-org-welcome-msg.preview.gitpod-dev.com/workspaces
2. Observe the org welcome message appear
3. Try signing out and in again, you should not see the message appear again

Documentation

TBD

/hold

[filiptronicek]

we use this localStorage item as a token, which the workspace list redeems in exchange for a modal with the organization join message.

[geropl]

I rebased the existing code and addressed two things:

1. the newUser parameter got replaced by a simple user.createdAt check
2. the handling of UpdateOrganizationSettings got a complete makeover (more to come in a follow-up PR)

The latter includes the call sites on dashboard - we literally had 6 places for adding a single field - enough is enough I guess 🙂

I did some testing in the (dedicated emulation) preview, especially around the changes (persistence of nested structs in OrganizationSettings) and it all seems to work nicely.

@corneliusludmann I would appreciate if you could do a short smoke test tomorrow, happy to set up the preview again if it has been gone - just 📯 me.

[corneliusludmann]

Adding some random findings as comments below while testing the org and user preferences. Not sure if every issue belongs to this PR, though.

[corneliusludmann]

---

What's odd?

1. Timeout will not be displayed in the yellow message: "its default timeout of MISSING HERE will be used." When explicitly set the workspace in the org, then it's okay. It only happens when there is no explicit value in the org settings page.
2. I can still edit the textfield and hit save. Sounds odd to me when I in fact the change does not have any effect.

[corneliusludmann]

Wrong text color in light theme (low contrast). In the user settings page, the notification text color seems to be okay.

[geropl]

Did a bunch of more testing, and the current version resembles the old behavior + the changes Filip did.

Really not fond of the humongous PR, but I don't know how to move forward in a timely manner. 🤷

[geropl]

/unhold

[filiptronicek]

Timeout will not be displayed in the yellow message: "its default timeout of MISSING HERE will be used." When explicitly set the workspace in the org, then it's okay. It only happens when there is no explicit value in the org settings page.

@corneliusludmann nice catch! The missing value in the warning banner seems easy enough to address, but I'm not sure if we should prevent users from entering new values in the field. On one hand, we totally could prevent saving new values when the org disables it. On the other, we don't usually couple user and org settings so much, since you can have multiple orgs (both in PAYG and in Dedicated), where the other orgs might possibly respect your timeout preferences.

To illustrate the user<>org settings decoupling, you can choose any editor you desire in the user settings, without it mattering if it's even supported by the org.