Perf: Consider replacing the use of Trace.unapply with Trace.parseOrNull

In ZIO 2.1.14, we've made some performance optimisations to the Trace methods.
See:

The Trace.parseOrNull (package private to zio package) returns null if it can't parse the trace or returns a ParsedTrace case class (instead of a Tuple), which avoids boxing

I'm not sure how much you use Trace.unapply but I just wanted to make you aware of these changes and potential optimisation.