Bug 1727916 - Convert several customizable toolbar item names to sentence case. r=fluent-reviewers,flod,emalysz

This required migrating several strings to Fluent, and the bulk of this patch
is those migrations. The rest of the items matched up with an entry in the app
menu, so those items were switched over to use the app menu strings, and one
had to be copied in order to avoid adding a tooltip to the app menu item.

Differential Revision: https://phabricator.services.mozilla.com/D124270

It was downgraded to investigate some windows crashes which ended up
being a crossbeam issue. So update it again to get fixes to some
crossbeam races.

Differential Revision: https://phabricator.services.mozilla.com/D125051

Bug 1727261 - Timeout Sqlite transaction async functions to properly roll back and interrupt the transaction. r=asuth

If the passed-in async function never resolves the transaction could stay alive forever, this timeouts after
TRANSACTIONS_QUEUE_TIMEOUT_MS (5 minutes as of now) and roll backs the transaction.
A telemetry keyed scalar is added to track callers causing these timeouts and optimize them in the future.

Differential Revision: https://phabricator.services.mozilla.com/D124187

Differential Revision: https://phabricator.services.mozilla.com/D124186

Add a pref to manage Sqlite.jsm logging, default to reporting Errors.
Change some of the logging to more coherently report warnings, errors and debug info.
Reuse the same logger for all the objects, just change the prefix.

Depends on D124184

Differential Revision: https://phabricator.services.mozilla.com/D124916

initiatedTransaction seems less confusing about the fact Sqlite.jsm initiated this
transaction, rather than something else (that may happen with wrapped connections).

Differential Revision: https://phabricator.services.mozilla.com/D124184

This commit modifies test_interfaces.js to also test the exposed interfaces
in the WebAssembly namespace. We have conditional features that we'd like
to have confidence that we're not accidentally exposing to web content.

Currently there are:
  * WebAssembly exceptions, enabled only in nightly with a default-off pref
  * mozIntGemm accelerator function, available only in system or addon principals

Depends on D120731

Differential Revision: https://phabricator.services.mozilla.com/D120732

The semantics of the try-delegate Wasm exception handling instruction
was recently changed in this spec discussion:

  https://github.com/WebAssembly/exception-handling/issues/176

This patch adjusts compilation and validation to match the new
semantics, which allows delegate to target any block.

Differential Revision: https://phabricator.services.mozilla.com/D124424

Bug 1726619 - Replace MOZ_LOW_PARALLELISM_BUILD with automated heuristic parallelism based on memory usage, and use for hazard builds r=firefox-build-system-reviewers,glandium

Differential Revision: https://phabricator.services.mozilla.com/D123147

Differential Revision: https://phabricator.services.mozilla.com/D125094

Differential Revision: https://phabricator.services.mozilla.com/D125093

Differential Revision: https://phabricator.services.mozilla.com/D125092

This was written by taking the text from here and deleting bits:
https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/Running_Automated_JavaScript_Tests

(Since I initially wrote this patch, that page was removed.)

Notes:

`./mach jstests -h` prints a short mach-specific help message, instead of the full output of `jstests.py -h`. We should probably fix that somehow, because requiring `./mach jstests -- -h` is silly.

The MDN version says "The jstests test suite also includes some tests from web-platform-tests. By default, these are only run when no tests paths are specified; this can be overridden by the --wpt=enabled flag.", but I wasn't sure if that would still be true after the Great Test Realignment, so I left it out.

I've never used `jstestbrowser` before, so I left the content mostly unchanged.

Differential Revision: https://phabricator.services.mozilla.com/D113689

This fixes a crash in our test harness, see
https://github.com/koush/AndroidAsync/issues/685.

Differential Revision: https://phabricator.services.mozilla.com/D124924

Differential Revision: https://phabricator.services.mozilla.com/D124923

Differential Revision: https://phabricator.services.mozilla.com/D125019

Differential Revision: https://phabricator.services.mozilla.com/D125018

Differential Revision: https://phabricator.services.mozilla.com/D125017

Differential Revision: https://phabricator.services.mozilla.com/D125067

Note that we don't appear to support 32-bit on mac so it'd be redundant to check for it.

Differential Revision: https://phabricator.services.mozilla.com/D124919

Differential Revision: https://phabricator.services.mozilla.com/D125026

Differential Revision: https://phabricator.services.mozilla.com/D124977

Bug 1715980 - Fix the calendar keyword in Calendar::GetBcp47Type docs; r=platform-i18n-reviewers,dminor DONTBUILD

Differential Revision: https://phabricator.services.mozilla.com/D124982

Differential Revision: https://phabricator.services.mozilla.com/D124954

Bug 1726416 - Update testcase for Arabic subtending marks (from bug 1599841) now that harfbuzz handles the number-directionality issue internally. r=emilio

We can no longer use direction overrides to create the test vs reference renderings here,
because of how harfbuzz now handles the numeral directionality internally. So it's difficult
to come up with a testcase that verifies the exact rendering of the subtending mark + digit(s)
combinations.

What we can do, though, is verify that a single digit combines with the subtending mark
without affecting its overall width; and that a double-digit number *does* increase the
width. These two conditions are unlikely to both hold unless the rendering is behaving
correctly.

(FWIW, Chrome Canary passes these new test versions, as it also uses a recent harfbuzz;
Safari currently fails, as Core Text doesn't support the subtending marks in the same
way, if at all.)

Differential Revision: https://phabricator.services.mozilla.com/D124902

Differential Revision: https://phabricator.services.mozilla.com/D124822

Differential Revision: https://phabricator.services.mozilla.com/D122989

Differential Revision: https://phabricator.services.mozilla.com/D125057

Bug 1729519 - Correct amount of places.sqlite-wal read and writes to cover correct amounts after bug 1727783. r=mak

Differential Revision: https://phabricator.services.mozilla.com/D125064

Differential Revision: https://phabricator.services.mozilla.com/D124657

Differential Revision: https://phabricator.services.mozilla.com/D124833

Differential Revision: https://phabricator.services.mozilla.com/D124987

Details in https://bugzilla.mozilla.org/show_bug.cgi?id=1721897#c5

Differential Revision: https://phabricator.services.mozilla.com/D121153

Bug 1729867 part 5 - Use same argument order for NewObject and NewObjectWithGivenTaggedProto. r=jonco

Depends on D125045

Differential Revision: https://phabricator.services.mozilla.com/D125046

Bug 1729867 part 4 - Remove ObjectFlags argument from NewObject and NewObjectWithGivenTaggedProto. r=jonco

Depends on D125044

Differential Revision: https://phabricator.services.mozilla.com/D125045

Depends on D125043

Differential Revision: https://phabricator.services.mozilla.com/D125044

Depends on D125042

Differential Revision: https://phabricator.services.mozilla.com/D125043

Differential Revision: https://phabricator.services.mozilla.com/D125042

Bug 1729689 - Do not require nsITimerCallback implementations to implement nsINamed on release or beta, as runnables don't have names there, r=smaug.

Differential Revision: https://phabricator.services.mozilla.com/D124910