Add 8, 12, 24 hours timeout option and respective translations.

[rarepops]

Might need some help with Bengali as well as Google Translate says that

"hour" = "ঘন্টার"
"1 hour" = "1 ঘন্টা"
"4 hours" = "4 ঘণ্টা"
"8 hours" = "8 ঘন্টা"

There are subtle differences I am not well versed in and don't know which is the correct way.

See: https://community.bitwarden.com/t/add-8-12-and-24-hours-timeout-options/29996

[CLAassistant]

All committers have signed the CLA.

[rarepops]

Also, it seems when I am trying to build, it gets stuck, so I couldn't actually test it

[./src/popup/images/logo-dark@2x.png] 43 bytes {mini-css-extract-plugin} [built]
    [./src/popup/images/logo-white@2x.png] 44 bytes {mini-css-extract-plugin} [built]
        + 9 hidden modules

However, trying to add whatever was built will give me 2 warnings:

  "applications": {
    "gecko": {
      "id": "{446900e4-71c2-419f-a6a7-df9c091e268b}",
      "strict_min_version": "42.0"
    }
  },

and

"sidebar_action": {
    "default_title": "Bitwarden",
    "default_panel": "popup/index.html?uilocation=sidebar",
    "default_icon": "images/icon19.png"
  }

[eliykat]

Hi @Rares95, thanks for the PR. Just a heads up that all our translations are managed by CrowdIn. This means that you only need to add the UI strings to en/messages.json (in English), and CrowdIn translators will handle everything else. It also means that we can't accept any changes to the other messages.json files via Github, as they'll be overwritten the next time CrowdIn translations are merged across.

As a starting point, can you please revert all your changes to all other messages.json files. I'll then schedule this for further review.

[rarepops]

@eliykat Done! Please review ebf2d1e

[eliykat]

Hey @Rares95, thanks for making those changes so quickly. I'll raise this internally to see if we can progress to code review. I'll keep you posted.

[cscharf]

Please see community forum thread for feedback and discussion points. Thanks @Rares95 !

[FranciscoKloganB]

Great work! Considered opening a PR for this as well. Glad to see someone beat me to it and even included the solution.

[Hinton]

I believe this pull request is no longer necessary since we've added a "Custom Vault Timeout" option which will be included in the next release, #2048 which should allow arbitrary timeouts.