Initial work to switch to tracing

[CosmicHorrorDev]

Resolves #2177

cc @taylor1791 (Sorry for the slight delay. Forgot it was Halloween weekend)

This is the initial work to switch from log to tracing

Roadbumps

• Tracing does not support dynamic levels or targets for the event!() and enabled!() macros which led to some ugly macros
• I couldn't find a proper way for tracing to detect the log level set in log world (e.g. RUST_LOG=debug with env_logger), so both tracing and log are checked for dynamic bits
  • Worth noting that the log feature of tracing pulls in log anyways, so it doesn't add any extra deps

Future Work

It would probably be worthwhile to have some spans setup for tracking calls throughout the library, but I'll leave that to someone else since life is getting busy again

[gitmalong]

Does your work include emitting traces that follow the OpenTelemetry db convention? https://opentelemetry.io/docs/reference/specification/trace/semantic_conventions/database/

That would just be awesome.

[abonander]

@CosmicHorrorDev do you mind rebasing this please?

[CosmicHorrorDev]

@gitmalong I doubt it. I kept the messages as is since the focus of this PR is just to switch the logging framework from log to tracing

---

@abonander Finished rebasing. Should be good for a review

[abonander]

This looks good! I remember looking into tracing and being annoyed that the level of an event had to be a constant, I'm glad you found a workaround.

[ShayBox]

log_statements requires log::LevelFilter, maybe a tracing_statements, built-in enum, int, or re-exported enum so an additional dependency isn't required for a single type

[CosmicHorrorDev]

I would leave a comment on #2177 instead since that's the pseudo tracking issue for the tracing switch