Expose ZoneSpecification parameters for package stack_trace

[feinstein]

Reopening after dart-lang/stack_trace#167 was closed because of the repo's migration.

Closes #1864 exposing several parameters from the ZoneSpecification for the package stack_trace.

This change will allow apps to have more control over the ZoneSpecification they need, when using the stack_trace package. For example, for security reasons many apps will override the PrintHandler, so no prints are exposed in production, but currently it's impossible to do it when using this package.

This is actually the main reason why I submitted this PR, but since I was at it, I thought it would be better to expose all other missing parameters, in case others need them.

[feinstein]

@devoncarew @lrhn I migrated this PR from the old repo, I would appreciate if you could review this, as the only reason why I don't use the stack_trace package in my app it's because I can't override the PrintHandler, and I have to do it for security reasons, so no prints are exposed in production.

Since I was going to expose the PrintHandler, I thought it would be better to just expose all the others, if anyone else needs them.

[lrhn]

I'm not sure this is necessary.
If you do:

runZoned(
  zoneSpecification: someSpec,
  () => capture(...));

it should create a zone with all the overrides you want, and then a nested zone for capturing stack traces, which only has access to what that parent zone exposes.

[feinstein]

Does this work with guarded zones too? Because I need to intercept exceptions and prints.

Does nesting zones introduce any performance impacts?