Modify AvTrace call chain to use params ReadOnlySpan<object> instead of an array

[h3xds1nz]

Fixes #9467 Reference #9463

Description

More of a complex fix, modifies the call chain to make use of the latest .NET features.

• I've used Span<object> instead of ReadOnlySpan<object> as the parameters array has always been mutated by the trace class, hence I didn't want to currently change the behaviour.
• Builds on the original intention of Reduce allocations when tracing routed events #6700
• The fixes should be compatible with my other PR too, Spanify AntiFormat function in AvTrace, decrease allocations, improve perf #9361 and Fix InvalidOperationException in AvTrace and improve general thread-safety #9352.
• ArrayList replaced with pre-allocated array and used interpolation for building the trace data.
• Modifies the AvTraceMessages.tt for completion.
• The overall cost of AvTrace / AvTraceMessages will be greatly reduced.

Customer Impact

Improved performance when tracing is active, decreased array allocations per each executed trace, smaller assemblies due to the function removal.

Regression

Fixes the ref held by _traceArguments from #6700

Testing

Local build, app run with tracing, comparing outputs of release/PR.

Risk

Low, the actual change is small and was reviewed/tested.

Microsoft Reviewers: Open in CodeFlow

[Alexgoon]

Hi there! Could you please update us on the status of this pull request? It's important for DevExpress components, and we're eager to know if you plan to merge it.

[h3xds1nz]

Hey @Alexgoon, I'm gonna CC a few guys from the wpf team just to be sure it doesn't get lost.

cc @pchaurasia14 @dipeshmsft

[Alexgoon]

Hi again,
I see the merging process has started - thanks for that! However, it looks like it’s stalled. Could you let me know if you plan to include this PR in the upcoming .NET 9 release?

[pchaurasia14]

@Alexgoon - We will be including this PR for upcoming test cycles, and it will go in for .NET 10.

[Alexgoon]

@pchaurasia14, thanks for the clarification! We were hoping the PR would be merged into .NET 9 since it addresses the issue described in #9467, which surfaced in .NET 9. After migrating to the latest version, a lot of our memory-related tests started failing.

I also noticed another PR (#9463) that might help resolve the memory leak issue. Do you have any plans to merge it into .NET 9, or will the memory issue (#9467) be handled as part of another fix?