Remove generation of trace files from CI and release process

[bocchino]

The CI process and the release process generate trace files and attempt to use them when running the native build. However, as far as I can tell, these trace files have no effect on the native build. The native build seems to use only the trace files that are checked into the FPP repo.

Can we please remove the generation of trace files from CI and the release process? I think manual management of these files is working fine, and removing the trace generation step would speed up the process. Especially for CI, this process is becoming a developer bottleneck, as the native builds take a long time, and they run on every merge to main or to a PR to main.

[LeStarch]

I question that the manual process works. fpp-to-json was broken when running on Ref for a period of ~9months due to a failure to update tracing.

It would be much better to get the tracing run in CI to properly influence the resulting binaries. However, if the concern is the native-build time, then it would be reasonable to pull this step out into a release only step.

[LeStarch]

Discussed this with @bocchino. The issue was lack of UT coverage for the parts needing trace. Since native images are tested with UTs, then a failure to update trace will fail in that step.

Therefore, removing trace should be done.