fix(telemtry): remove redundant report_event during recovery

[fuyufjh]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

Our telemetry reports too many events. One of the cause is that some code path calls report_event() not only at the time something is created, but also on recovery, which is not expected.

Checklist

• I have written necessary rustdoc comments.
• I have added necessary unit tests and integration tests.
• I have added test labels as necessary.
• I have added fuzzing tests or opened an issue to track them.
• My PR contains breaking changes.
• My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
• My PR contains critical fixes that are necessary to be merged into the latest release.

Documentation

• My PR needs documentation updates.

Release note

[graphite-app]

This debug code with println! and backtrace capture appears to be temporary development scaffolding. While it's helpful for debugging telemetry calls during development, it should be removed before merging to prevent performance overhead and log spam in production. Consider using tracing or debug logging if this visibility needs to be preserved in a more controlled way.

Spotted by Graphite Reviewer

Is this helpful? React 👍 or 👎 to let us know.