The isError_ check uses a heuristic that calls the Function constructor
to determine if the given value is an Error object. This results in a
runtime violation in test suites that enforce Trusted Types.

Since Trusted Types are only supported in modern browsers (currently,
Chromium-based browsers), we can use a more straightforward heuristic in
environments where Trusted Types are supported.

Fixes #1910. See that thread for more details.

These might be useful for a function with a more restricted domain. But for
equals, which accepts two of literally anything, the short run was too short
to catch any problems and the long run tended to exceed the CircleCi timeout.

… main

* Fixes Trusted Types error in Chromium-based browsers
* Merges #1921 from @bjarkler
* Fixes #1910

This is mainly intended to support jasmine-browser-runner, which will load
a script that configures the env in between the two boot files (boot0.js and
boot1.js). The single-file boot.js is retained for now but will be removed
in a future release.

These properties are the only way to obtain runnable IDs, without which
you can't call the form of Env#execute that takes an array of IDs.

…ure and stopSpecOnExpectationFailure

The new names are more self-explanatory and consistent with jasmine-npm. The
old names are deprecated but still work.

[#178682783]

…nv#stopOnSpecFailure()

[#178373231]

…`Error` reasons on Node

[#179227413]