Add 12/24 hour lock options

[mcanning]

Hi! I recently converted from lastpass and noticed the maximum lock duration was 4 hours. This results in needing to re-login over the course of a single work day (which can be a minor annoyance) but was noticeable when trying to make the move.

I've added 12 and 24 hours here and updated locales, if you think this is too much clutter for the UI I would be more than happy to just use one or the other.

[CLAassistant]

All committers have signed the CLA.

[LaurentOngaro]

please, can you approve this PR, it's very very useful for me

[Clonkex]

OP needs to sign the CLA before the PR can be approved.

[mcanning]

OP needs to sign the CLA before the PR can be approved.

Done

[fbarbeira]

This is interesting, it would allow our users to unlock once per day their vault instead of two.

If I have to choose it would be better to add only an 8h option to accomplish the user goal of unlock one time per day.

[cscharf]

@mcanning , please revert all changes to the localization files, except for src/_locales/en/messages.json, that file "seeds" our crowdin integration for translation everywhere else, otherwise the translation links will break or fail to get updated in future syncs.

Also, for consistency across clients, this type of change would also need to be made in all other client repos that offer the same timeout options, including: web, desktop, mobile. This would also need to be controllable by policy and therefore in the web vault under user timeout policy the expanded options would need to be added there, as well as in the new business portal under the same (policies).

Let me know if you have any questions or concerns. I would also encourage you to use the Bitwarden Community Forums which has a section for submitting, voting for, and discussing product community contributions like this one if you need more assistance in requirements, areas to focus and final approval of approach, content, etc. before getting too far into the weeds.

[eliykat]

I'm closing this as inactive because change requests from September have not been actioned. There is a more current effort to revamp the timeout options here (which you're welcome to get involved in if you still want to help): #1851.