refactor(ses): Replace Rollup with Endo bundle

[kriskowal]

This change replaces the Rollup based bundle distribution files with bundles generated using the compartment mapper’s rudimentary bundler.

One negative consequence is that the minified bundle size increases by 2⨉ to 85KB.

Refs #175

merge target must be changed to master before merge

[erights]

LGTM

[erights]

The fact that there are only two, but with eight names, is amusing. No change suggested.

[kriskowal]

True. This is the effect of architectural drift in this case. Before I changed the SES shim to effect its API strictly using globals, there was a difference between the CJS, MJS, and UMD treatments. Rollup continued to emphasize the difference in its configuration options, but the difference amounted to nothing except a vestigial SES global introduced by the UMD version. The lockdown versions were of course briefly different. We’re retaining all of these only to ease the migration path. In the end, we really only need ses.cjs (with the CJS extension strictly to navigate RESM to NESM portability) and ses.umd.min.js.

[erights]

We should adopt some convention that we can check, for making sources of static authority stand out in our source files. Just noting. No change suggested at this time. Attn @dckc

[kriskowal]

This should also be a script that we run with Endo instead of Node, and it should be counted a design goal for Endo to accommodate injection of an attenuated FS and a decent DX for granting that capability to the script. For example, there might be some reasonable default filesystem attenuation for any Endo script run in the context of developer tools for a package, or at least a convenient piece of boilerplate we can add to package.json to grant that limited authority.

[erights]

"DX"?