[PM-1689] Add restriction to only encrypt fails on browser

[gbubemismith]

Type of change

- [X] Bug fix
- [ ] New feature development
- [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other

Objective

The PR for adding validations to ensure new encryption isn't called when the server doesn't support it works on all clients except the browser.

Code changes

The initial failure was due to the CipherService attempting to access the configApiService before it had been instantiated. To resolve this issue, I ensured the ConfigApiService was initialized within the main.background.ts file on the browser client side.

Before you submit

• Please add unit tests where it makes sense to do so (encouraged but not required)
• If this change requires a documentation update - notify the documentation team
• If this change has particular deployment requirements - notify the DevOps team
• Ensure that all UI additions follow WCAG AA requirements

[differsthecat]

This looks good, thanks @gbubemismith ! I had to double-check that we needed the ConfigApiService in the background, but it appears that we do as CipherService needs it.