Use Qt's public logging APIs rather than undocumented internals

[jnbooth]

Instead of exposing undocumented internal features of Qt, qtlogging.rs now exports q_critical, q_debug, q_fatal, q_info, and q_warning, equivalent to Qt's qCritical, qDebug, qFatal, qInfo, and qWarning. So instead of doing this:

qt_message_output(
  QtMsgType::QtInfoMsg,
  &QMessageLogContext::new(c"myfile.rs", 1, c"", c"default"),
  &QString::from(&format!("Test message: {x} / {y}"))
);

You can simply do this:

q_info!("Test message: {x} / {y}");

The file and line number are automatically filled in by the file and line built-in macros.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (cb64b22) to head (a3ddf73).

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1300   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           75        75           
  Lines        12772     12772           
=========================================
  Hits         12772     12772           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.