jimporter / lockbox-extension

…e#552)

…e#509)

* Replicate send-feedback to create a FAQ link component

admittedly a total copy/paste job and not certain if good for long term maintenance with potential for changes (like if/when one or the other becomes something else) versus making send-feedback abstract to take two and then split out later when either one changes to be something other than a simple link :thinking_face:

* redo open-faq to match send-feedback with telemetry updates

* update to use common ExternalLink widget

* Merge branch 'master' into telemetry_leif

* Nit: add line between MPL header and code

* Move copy event to fire on actual copy

* address indenting formatting and fxaid typo

* Better wrapping and indentation

* Fix malformed copy/paste mistake from 2bf1c50

* changed fxa metrics wording

* minor: consistent capital L in Lockbox

* update modified date

* changed entryDetails to itemDetails

* add username/pw specific copy events

* fix lint thing space

…zilla-lockwise#184

Note that this only applies to *new* installs of Lockbox, so existing users
will want to uninstall Lockbox, restart Firefox, and reinstall. This is
slightly inconvenient, but shouldn't be a problem in the long term.

…fox session

* added event recording

see changes to tldr section in docs/metrics.md

* address linting errors

* record item.id for itemAdded/addItemForm

* only record addClick when the button is actually clicked

* update to latest lockbox-datastore

* moved around some events + datastore metrics

* updated metrics doc to reflect current reality

* add feedback metric

* incorrect l10n id

* addressing jim's review

addressed some of Jim's comments, though not the last two questioning the right place  of

 telemetry.recordEvent("lockbox", "render", "manage");

and

 telemetry.recordEvent("lockbox", "render", "popupUnlock");

because I'm not sure what the right answer is there.

* fixed linting thing

This allows our webextension to record telemetry (events only at the moment)
by forwarding messages first through the background scripts (to pick up the
user's FxA user id) and then to the XPCOM extension.

Now that <https://bugzilla.mozilla.org/show_bug.cgi?id=1395879> is fixed, we
can update to the latest version of eslint (and plugins).

… somehow?)

Resolves mozilla-lockwise#20.