Expand browser tests to include canary browsers and run periodically against trunk

[kriskowal]

What is the Problem Being Solved?

We do not currently automation for early discovery of changes to browsers that will break before those changes are released by mainstream browsers.

Description of the Design

We do have a test that verifies that changes to ses do not break in modern browsers. We can extend the mechanism in browser-test and the add a similar CI job to run periodically against master with canaries.

The scope of this issue is narrow to browsers, but we also have ses-integration-test using eshost, running directly on any supported pure-JavaScript engine. We could subsume that into the scope of this issue or break it off.

The scope of this issue is limited to running lockdown to completion, but could be extended to also monitor for new property removals that require our attention. Generating issues automatically would be tremendous.

Security Considerations

Scaling Considerations

Test Plan

Compatibility Considerations

Upgrade Considerations

[kriskowal]

Will be closed by https://github.com/endojs/endo/pull/1978#pullrequestreview-2021005698