<!-- 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 -->
This will also make it break during build.

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

Co-authored-by: Rodrigo Nascimento <rodrigoknascimento@gmail.com>
Co-authored-by: Alan Sikora <alansikora@gmail.com>

Co-authored-by: Martin Schoeler <martin.schoeler@rocket.chat>
Co-authored-by: Tasso Evangelista <tasso.evangelista@rocket.chat>
Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>

* Change omnichannel office hours data structure

* Rename omnichannel office hours templates

* Renaming things from office hour to business hour

* Partially remove LivechatOfficeHour model

* remove obsolete setting

* Remove settings from the template

* Add support to cron jobs on omnichannel business hours

* Add dynamic template to omnichannel business hours

* Open and close business hours

* Remove references to LivechatOfficeHours

* Open and close business hour automatically on startup and setting changes

* Improve open and close business hours process

* Removing separated interfaces

* Apply suggestions from review

* Changing pt-br term

* General improvements on business hour layout

* Apply suggestions from review

* Remove online verification

* Change data structure

* Ignore if collection does not exist

Co-authored-by: Renato Becker <renato.augusto.becker@gmail.com>

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

* Enable typescript lint

* Move eslint-plugin-import to deve section