fix(ses,lockdown): make filenames in stacktraces clickable

[erights]

Staged on #2690

Description

Added two new stackFiltering: options

• 'omit-frames' -- Only omit likely uninteresting frames. Keep original paths.
• 'shorten-paths' -- Only shorten paths to text likely clickable in an IDE

This fills out the matrix of what should have been orthogonal options.
The existing 'concise' setting both omits likely uninteresting frames and
shortens their paths. The existing 'verbose' setting does neither.

The path shortening caused by either 'concise' or 'shorten-paths' is also enhanced with two new transformations, in order to make these paths easily and usefully clickable in an IDE like vscode.

• We would already shorten, for example

  'Object.bar (/vat-v1/.../eventual-send/test/deep-send.test.js:13:21)'
  

  to

  'Object.bar (eventual-send/test/deep-send.test.js:13:21)'.
  

  As of this PR, we would also shorten, for example

  'Object.bar (.../eventual-send/test/deep-send.test.js:13:21)'
  

  to

  'Object.bar (eventual-send/test/deep-send.test.js:13:21)'.
  

• As of this PR, we would would shorten, for example

  'Object.bar (file://test/deep-send.test.js:13:21)'
  

  to

  'Object.bar (test/deep-send.test.js:13:21)'.
  

  because the shorter string is a valid relative path, which is therefore usefully clickable.
  But we would still not shorten or transform, for example

  'file:///Users/markmiller/src/ongithub/endojs/endo/packages/eventual-send/test/deep-send.test.js:13:21'
  

  because three slashes are normally followed by an absolute path, which is therefore usefully clickable.

• This PR changes commit-debug.js from 'errorTaming: 'unsafe-debug' to errorTaming: 'unsafe' so that exiting programs whose initialization goes through commit-debug.js can benefit from stackFiltering: at all, as well as these new enhancements. TODO but this PR must also fix, by other means, the typescript line number bug that motivated 'unsafe-debug' in the first place. See (TODO link)

• This PR does not change that all this stackFiltering: logic is specific to v8. We should move and generalize this code so that it applies to all relevant JS platforms. TODO at least file an issue for that.

Security Considerations

none

Scaling Considerations

none

Documentation Considerations

Wherever we document the stackFiltering: rules, we should update those. This PR already updates such documentation within agoric-sdk itself.

Testing Considerations

stackFiltering: is hard to automatically test because there is no specified or portable behavior for the platform-provided stacks. Instead, we just have manual inspection tests, where you run it and visually sanity check the output. I have added such checks for the new options setting and manually sanity checked them.

Compatibility Considerations

The only observable change to existing programs is the more aggressive path shortening explained above. I doubt this will cause any compat problems, especially since the platform stack traces are unspecified anyway.

Upgrade Considerations

None.

• Update NEWS.md for user-facing changes.