Make getGlobal() work in strict mode

An update of https://github.com/metaweta/jasmine/commit/fb3e1acb09b4dbb9ccdbc15ce64b4a0e471f4541

ES5 strict mode does not promote an undefined 'this' to the global object.  The only way to get the global object in strict mode is to say 'this' while in the global scope.
Adding Compass as a dev dependency in order to build HTMLreporter CSS
Make exposure of addMatchers and addCustomEqualityTesters be on jasmine instead of inconsistent.
Moving a documented-up boot.js from the website back into core
Continuing boot change with docs
removed addMatchers from the global. This should have been in previous commit
Move clock from global to jasmine; provide a function to access the clock.
Env no longer automatically uninstalls the clock after each spec

- Behaves more like how we want plugins to behave

[#58281436]
Merge pull request #450 from slackersoft/manualClockUninstall

Env no longer automatically uninstalls the clock after each spec
Improve error message when a spec doesn't call the async callback within the default time interval
Remove now unused updateInterval that was being set in specs
Re-enable CustomMatchersSpec and update for current version of custom matchers
Remove an extra layer of wrapping for matchers/custom matchers

Helps reduce how nested custom matchers have to be for users as well as
Jasmine internal matchers

[#59161378]
Stop passing in queryString to HTMLReporter, it is unused
A spec without expectations is considered passing

- Specs are passing by default unless told otherwise
- Getting the result.status of a spec before the spec has run is now
  undefined instead of pending

[finishes #59422744]
Remove TODO: should be easier to load polyfill for timeout functions as Jasmine does not get references to these functions until boot.js is loaded
Use toThrowError instead of toThrow in places where we are expecting an error
Move next spec/next suite ids into closure

No longer exposing these from the environment
Remove addCustomEqualityTester and addMatchers from global

These functions are available on the jasmine namespace
Move additional methods from Env prototype to env closure

- Users can no longer spelunk the spec tree from topSuite
- Users no longer have access to currentSuite/currentSpec
- Other miscellaneous (arguably less useful) methods have also been tucked
away into the closure, like suiteFactory