feat: support deno

Apply mount-observe and system-observe plug fix to 6.x release branch

Fix: Add mount-observe and system-observe plug to snap

ci: sync with 6.x (do not delete branch)

* fix: new revision with bridge epoch

* fix: newest 6.x revision epoch revised

* Bump Rocket.Chat version to 6.1.6

* chore: bump version to 6.2.0

* fix: version comparison in candidate releases

* chore: add core team notifications

* fix: always run notification step

* chore: version context in notifications

* new: add tests to force release workflow

* Bump Rocket.Chat version to 6.2.8

* Bump Rocket.Chat version to 6.2.9

* Bump Rocket.Chat version to 6.2.10

* Bump Rocket.Chat version to 6.2.11

* Bump version to 6.3.0

* Bump Rocket.Chat version to 6.2.12

* Bump Rocket.Chat version to 6.3.1

* Bump Rocket.Chat version to 6.3.2

* Bump Rocket.Chat version to 6.3.3

* Bump Rocket.Chat version to 6.3.4

* Bump Rocket.Chat version to 6.3.5

* Bump Rocket.Chat version to 6.3.6

* Bump Rocket.Chat version to 6.3.7

* Bump Rocket.Chat version to 6.3.8

* Bump Rocket.Chat version to 6.4.0

* Bump Rocket.Chat version to 6.3.9

* Bump Rocket.Chat version to 6.3.10

* Bump Rocket.Chat version to 6.4.1

* Bump Rocket.Chat version to 6.4.2

* Bump Rocket.Chat version to 6.4.3

* Bump Rocket.Chat version to 6.4.4

* Bump Rocket.Chat version to 6.4.5

* Bump Rocket.Chat version to 6.3.11

* Bump Rocket.Chat version to 6.4.6

* Bump Rocket.Chat version to 6.3.12

* Bump Rocket.Chat version to 6.4.7

* Bump Rocket.Chat version to 6.4.8

* Bump Rocket.Chat version to 6.5.0

* Bump Rocket.Chat version to 6.5.1

* Bump Rocket.Chat version to 6.5.2

* Bump Rocket.Chat version to 6.4.9

* ci: don't calculate greater than as it is all consuming and can fail for lack of context (#67)

* chore: pulling force release workflow from develop

* ci: don't calculate greater than as it is all consuming and can fail for
lack of context

If there are two version strings, and we perform a greater than, in this
way, since every next step doesn't know about the last one, it can
result in a false positive.

Instead, if we test if A is less than B, for the three steps, if the
previous did not cause a return, means we are still ok. Therefore this
current step is all we need.

---------

Co-authored-by: debdutdeb <debdutdeb@users.noreply.github.com>
Co-authored-by: rocketchat-github-ci <rocketchat-github-ci@users.noreply.github.com>

* chore: pulling force release workflow from develop

* ci: don't calculate greater than as it is all consuming and can fail for
lack of context

If there are two version strings, and we perform a greater than, in this
way, since every next step doesn't know about the last one, it can
result in a false positive.

Instead, if we test if A is less than B, for the three steps, if the
previous did not cause a return, means we are still ok. Therefore this
current step is all we need.