Bug 857901: Increase keyboard character-delete speed

UX informs me that 75ms seems to be a good interval, and that the
initial delay is fine where it is.
Bug 877615 - [MMS] New message composer: Recipients field stays expanded after discarding a previous multi recipient message - r=gnarf37

- #messages-recipients-list is declared "singleline" in markup
- Test to enforce recipient list always begins in singleline mode

Signed-off-by: Rick Waldron <waldron.rick@gmail.com>

Closes gh-10193
Bug 875690 - [MMS] [UX] Thread view. Wrong alignment of elements - r=gnarf

Closes gh-10091
Bug 879273 - linter fixes, r=Rik
Merge pull request #10188 from fabi1cazenave/linter-bug879273

Bug 879273 - linter fixes, r=Rik
Merge pull request #10090 from jld/delete-faster

Bug 857901: Increase keyboard character-delete speed
Bug 845760 - long press on period key does not show special character menu on French keyboard, r=dflanagan
Bug 877683 - [MMS] Compose field obscured by subheader r=gnarf37

In accordance with the UI specification, update the interaction between
the "subheader" elements and the Compose field. Specifically, this
means:

- Some elements should never obscure the Compose fields (when active,
  they should instead "push" the Compose field downward if it is
  rendered at maximum height. These elements are:
  - The Recipients List (or "To: Field")
  - The "MMS Max Length" notifications
  - The "Carrier" element
- The "Message Convert Notification" should render overlaid on the
  Compose field.

To implement the specified behavior, this commit includes the following
changes:

- The "subheader" elements
  - Markup has been updated to differentiate between notifications that
    should push the Compose field downward and those that are "overlaid"
    on the Compose field.
  - Styling has been updated to ensure that the appropriate elements
    trigger resizing of the "subheader" (while taking care not to alter
    the visual presentation of these elements)
- Compose field height recalculation:
  - Scheduled to occur whenever changes in the DOM may change the height
    of the "subheader"
  - Removed logic that triggered recalculation in response to the
    global `hashchange` event (the above change obsoletes this more
    simplistic heuristic)
- Maximum input height calculation now has been generalized to honor any
  change in height to the "subheader"
- The Compose field's height calculation logic has been updated:
  - Modify the input's scoll offset (in order to prevent undesired
    changes in position)
  - Comments and variable names updated as appropriate
  - Remove meaningless CSS calculation (setting the `bottom` attribute
    of a `position: static;` element)
Bug 809607 - Abort transactions / sync if account was removed r=lightsofapollo
Merge pull request #9852 from lightsofapollo/bug-809607-cleanup

Bug 809607 - Abort transactions / sync if account was removed r=lightsof...
Merge pull request #8361 from taratatach/add_alternate_punctuation

Bug 845760 - long press on period key does not show special character me... r=davidflagan
Bug 869903 - Set iframe background to app background using firstpaint, r=vingetun
Bug 877487 - GELAM only update to fix issue where switching between sdcard default storage and internal makes attachments useless.
bug 867038 - allow alarms with/without vibrate and ring tone
Merge pull request #10197 from lightsofapollo/bug-877487-gelam-update

Bug 877487 - GELAM only update to fix issue where switching between sdca...
Merge pull request #10097 from mikehenrty/bug-867038-alarms

Bug 867038 - Allow alarms with/without vibrate and ring tone