<!-- This is a pull request template, you do not need to uncomment or remove the comments, they won't show up in the PR text. -->

<!-- Your Pull Request name should start with one of the following tags
  [NEW] For new features
  [IMPROVE] For an improvement (performance or little improvements) in existing features
  [FIX] For bug fixes that affect the end-user
  [BREAK] For pull requests including breaking changes
  Chore: For small tasks
  Doc: For documentation
-->

<!-- Checklist!!! If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. 
  - I have read the Contributing Guide - https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat doc
  - I have signed the CLA - https://cla-assistant.io/RocketChat/Rocket.Chat
  - Lint and unit tests pass locally with my changes
  - I have added tests that prove my fix is effective or that my feature works (if applicable)
  - I have added necessary documentation (if applicable)
  - Any dependent changes have been merged and published in downstream modules
-->

## Proposed changes (including videos or screenshots)
<!-- CHANGELOG -->
<!--
  Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
  If it fixes a bug or resolves a feature request, be sure to link to that issue below.
  This description will appear in the release notes if we accept the contribution.
-->

<!-- END CHANGELOG -->

## Issue(s)
<!-- Link the issues being closed by or related to this PR. For example, you can use #594 if this PR closes issue number 594 -->

## Steps to test or reproduce
<!-- Mention how you would reproduce the bug if not mentioned on the issue page already. Also mention which screens are going to have the changes if applicable -->

## Further comments
<!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... -->

* Messages raw model rewrtite to ts

Co-authored-by: Pierre Lehnen <pierre.lehnen@rocket.chat>

Co-authored-by: dougfabris <devfabris@gmail.com>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>

Co-authored-by: Diego Sampaio <chinello@gmail.com>

* Fix regressions

* Split ConnectionStatusContext from ConnectionStatusProvider

* Split RouterContext from RouterProvider

* Split TranslationContext from TranslationProvider

* Update Storybook

* Refactor ConnectionStatusAlert

* Fix eslint issues

* Add SessionContext

* Add SidebarContext

* Fix RouterProvider

* Add useSubscription

* Deprecate ErrorAlert

* Prefer read unread from Session

* Add ToastMessagesContext

* Deprecate useSetSetting

* Fix SetupWizardRoute

* Fix ToastMessagesProvider

* Fix useSubscription

* Add Logo

* Add useIsMounted

* Refactor SetupWizardRoute

* Fix useReactiveValue loop

* Refactor SetupWizardState

* Add some skeleton components

* Add missing Storybook stories

* Add missing Storybook stories

* Refactor Storybook mocks

* Fix useIsMounted

* Refactor ConnectionStatusAlert styles

* Refactor ConnectionStatusContext

* Improve useObservableValue

* Remove some references to Meteor

* Add SettingsContext

* Remove some references to toastr and TAPi18n

* Fix translate.has function

* Remove superfluous argument

* Add storybook-static to gitignore

* Fix lint warnings

* Split providers from components

* Add UserContext

* Add AuthorizationContext

* Add useRole

* Add ServerContext

* Add missing hooks for client APIs

* Add helper to create observable values

* Add missing ServerProvider

* Don't trust the gap between initial value and autorun in reactive sources

Co-authored-by: Oliver Jägle <github@beimir.net>
Co-authored-by: vickyokrm <vickyokrm@gmail.com>

* The Livechat translation files have been moved to Rocket.Chat translation package.

* Fix en translation on livechat

* Add README

Implementing the administration setting for the frequency of notifications about changing user's password. #2995

This will make Meteor ignore changes on this folder which will prevent rebuilds of whole livechat package.

For local development it is recommended to run the livechat app individually like on run.sh file.