report errors to FES when appropriate

[tomholub]

do actual error reporting in separate PR as it's more complex

Originally posted by @tomholub in #3015 (comment)

[tomholub]

Difficulties:

• need to access storage on every error report (sometimes it's the storage that failed in the first place)
• need to figure out which user to authenticate as (easy on flowcrypt urls as they have acctEmail in url)
• in content scripts (no acctEmail in url) need to figure out which user is running. Worst case just grab first user from storage
• think about implications when errors happen in background page (also no acctEmail)

[tomholub]

For now, we have disabled all error reporting on enterprise builds, which solves the issue for now.