Omit module-internal lines from stack trace when resource throws exception about zerodsc HOT 3 OPEN

Implementation ideas:

1. Rewrite the .ScriptStackTrace property with a string that omits a bunch of the stack trace.
2. Catch the exception at lowest point in the call stack that is inside ZeroDSC, and somehow re-throw that same exception at the highest point in the call stack.
3. Change the way [ConfigStep] objects are set up such that the call stack between Invoke-ConfigStep and the underlying resource is minimized.

from zerodsc.

(1) is complicated by .ScriptStackTrace being a read-only property.

try
{
    throw
}
catch
{
    $_.ScriptStackTrace = 'new trace'
}

results in

'ScriptStackTrace' is a ReadOnly property.
At C:\Users\un1\Desktop\test.ps1:7 char:5
+     $_.ScriptStackTrace = 'new trace'
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : PropertyAssignmentException

from zerodsc.

It doesn't seem like (2) would work because .ScriptStackTrace is populated when the exception is first thrown. So catching and re-throwing doesn't change its contents. For example,

function f1 { throw 'exception in f1' }
function f2 { try { f1 } catch { return $_ } }
function f3 { $e = f2; return $e }
function f4 { $e = f3; throw $e }

Describe 'delayed re-throw' {
    It 'test' {
        f4
    }
}

results in

Describing delayed re-throw
 [-] test 18ms
   RuntimeException: exception in f1
   at f1, C:\Users\un1\Desktop\test.ps1: line 1
   at f2, C:\Users\un1\Desktop\test.ps1: line 2
   at f3, C:\Users\un1\Desktop\test.ps1: line 3
   at f4, C:\Users\un1\Desktop\test.ps1: line 4
   at <ScriptBlock>, C:\Users\un1\Desktop\test.ps1: line 8

from zerodsc.