[#94] Terminology

[dcastro]

Description

• "Slack entrypoint": It's fine to use the word "entrypoint" internally, but not in user-facing messages/documentation. We should say "A message's context menu ⋮" instead
• "timeshifts": this is not common terminology. We should use "time changes" or "clock changes" instead, see examples of use in the wild:
  • https://www.timeanddate.com/time/change/portugal/lisbon
  • https://www.worlddata.info/europe/portugal/timezones.php
• "translate time references": Not really sure "translation" is what we mean here, I think "convert time references" would make more sense
• "time refs": Do not use abbreviations like "refs" in user-facing messages. Spell them out in full, i.e. "time references"

  Related issue(s)

Fixed #94

:white_check_mark: Checklist for your Pull Request

Related changes (conditional)

• Tests

  • [x] If I added new functionality, I added tests covering it.
  • [x] If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.

• Documentation

  • [x] I checked whether I should update the docs and did so if necessary:
  • README
  • Haddock

Stylistic guide (mandatory)

• [x] My commits comply with the policy used in Serokell.
• [x] My code complies with the style guide.