Need source-prefix-based stackframe filter

[erights]

#447 give us a start on conveniences needed for treating compartments as filtering "topics" for console output. We expect the dominant use of compartments to be a compartment per package, where a package is identified with a specifier string corresponding to a source location. As of #447 our stacks have lots of infrastructure frames in them, creating visual noise and making it hard to find the frames of actual interest. It would be nice for the default conveniences for these two forms of filtering to be coordinated, so that it is each to filter out a package's code both from console calls originating from that package and the stack frames of code in that package.

[erights]

Our current Error taming provides a getStackString which #447 uses to render unfiltered stacks.
This issue requires the Error taming to also support the proposed getStack, so that we can accurately filter rather than scraping text.

[erights]

Causeway filtered stacks by source prefix to good effect. In the graph visualizations, it would first collapse out turns for which no frames survived that filter. Those turns are pure infrastructure, for example from an asynchronous programming abstraction like a promise combinator.

[erights]

We took a big first step towards this with the stackFiltering option. But it (as well as several other options) also need to accept configuration data.

See #578