<!-- 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... -->
Looks like the update of de dep had breaking changes and now uses promises at some calls. This PR fixes those promise usages and converts the file to TS (hopefully it helps us to spot the error in the future)

<!-- 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.
-->
Added a validation in the prop used for sorting (loweCaseName) checking for a prop that only exists in discussions (prid)

<!-- 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
Steps to reproduce:

1. Log in to the [rocket.chat](http://rocket.chat/) (version 4.8.0-rc.1)
2. Click on the button Display and select the option Sort by : Name 

Actual result:

-   The discussions were not sorted by name in all types of Group: Unread, Favorites and Types 

![image](https://user-images.githubusercontent.com/20212776/172384754-3d33c76b-926b-4814-bb2f-22c7f0f914ae.png)

Expected result:
The discussions should be sorted by name

## 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... -->

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

* Remove snap related files from project https://github.com/RocketChat/Rocket.Chat/pull/25790/commits/5f3b683d29e2d2058a4c57465f245dd0984791bf

Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz>

* Correct directory capitalization

* Move some message blocks

* Move some message blocks

* Move some elements

* Move some elements

* Segregate message and thread preview at top-level

* Add `ColorElement`

* Add `MessageBodyPreview`

* Detach markup from message

* Cascade some markup styles

* also render origin

Co-authored-by: gabriellsh <gabriel.henriques@rocket.chat>

* Bumb meteoer-node-stubs to version 1.2.3 to fix issue #25460

* yarn.lock

Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz>

* refactor: refactor matrix bridge to support testing + unit tests

* fix: fix conflict

* fix: types on test

* fix: fix tests

* chore: rename bridged to federated

* chore: remove duplicated config

* fix:  fix yarn.lock

* chore: add migration for the renamed field

* chore: fix lint

* fix: type

* Invisible to Offline

* accomodate #25265  (Convert to tsx)+

* Rename UserStatusMenu.js to UserStatusMenu.tsx

* Use correct file path

Co-authored-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
Co-authored-by: dougfabris <devfabris@gmail.com>

* Messages raw model rewrtite to ts

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

Co-authored-by: gabriellsh <gabriel.henriques@rocket.chat>

* fix(fuselage): adding sequential param to Message Component

* chore: updating fuselage version

* fix: updating yarn.lock

* fix yarn.lock

* Update fuselage

* remove dev deps

Co-authored-by: gabriellsh <gabriel.henriques@rocket.chat>