[MS] Adds accept tos modal

[Max-7]

Closes #7633
Depends on #8471

To test:

1. Don't forget to recompile, python make.py i && python make.py ei
2. Start the testbed
3. Open electron. On the device page, note the org name
4. Use the little script python update_tos.py <OrgName>
5. Log in to the org

Don't forget to change the locale to check if the link is updated, you can add additional locales to update_tos.py, change their name, use en_US or en-us or en or some kind of variations to check if the GUI manages to find the most appropriate version.

# upload_tos.py. It needs requests.
import requests
import sys

response = requests.patch(
    f"http://localhost:6770/administration/organizations/{sys.argv[1]}",
    headers={"Authorization": f"Bearer s3cr3t"},
    json={"tos": {
        "en_US": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
        "fr_BE": "https://www.youtube.com/watch?v=hEmODTcKJmE",
    }},
)

print(response.status_code, response.content)

• Keep changes in the pull request as small as possible
• Ensure the commit history is sanitized
• Give a meaningful title to your PR
• Describe your changes
• Link any related issue in the description

[FirelightFlagboy]

I don't see tests for that feature

[mmmarcos]

The "normal" use cases seem to work fine:

1. ToS defined in server, user logins, ToS dialog is displayed, user accepts ToS, login (OK)
2. User logout, then login, no ToS dialog is displayed (OK)
3. User logout, ToS updates in server, user login --> same as 1 (OK)

Issues

Wrong login status

• User is logged out
• TOS are updated in the server
• User tries to login, accepts the new TOS
• Login status is not updated (KO)
  
• Go to home, shows user is logged-in
  
• Return to org, login status is still offline (KO)
• Logout, then login, -- login status is online (OK)

App state if logged-in during ToS update

If the user is logged-in and the TOS are updated on the server. The application behaves unexpectedly:

• At first, nothing seems to change from the user perspective (menus are accesible, workspaces can be created, folders can be opened, files can be imported, etc.).
• However, some actions like attempting to sharing a workspace, result in an unrelated error:
  
  This is very disturbing for the user, who is most certainly not aware of TOS update, and the apps seems to fail wirhout any reason.

What should be done in this case it should be carefully discussed:

• should the user be forced to log out? not great, since it could be importing files or editing a document...
• should we ask for TOS acceptance, but let them continue using until next login? asking for acceptance could potentially also block a current user operation
• should we ignore TOS update until next login? this seems the more natural and user-friendly alternative. Although it may need changes on the current TOS logic.

[mmmarcos]

Minor suggestions

[mmmarcos]

Some comments otherwise LGTM (I've mostly reviewed changes to the server/ directory).

[AureliaDolo]

I've looked mostly at the libparsec part and it's looking good.

[AureliaDolo]

It's an idea for later. but could that event be useful in some other places too ?

[mmmarcos]

LGTM (server part)