Remove undefined behavior from QMessageLogContext

[jnbooth]

According to the safety documentation for CStr::from_ptr, the pointer must be non-null. Currently, the functions for QMessageLogContext do not check for null pointers. This PR adds those checks, removing the undefined behavior.

Note: cxx-qt-lib's qtlogging code is noticeably messy. In addition to the above undefined behavior, it has extraneous unsafe specifiers and a pointless const assertion that was probably supposed to occur on the C++ side, and its functions are in the global namespace rather than rust::cxxqtlib1. It also solely exposes undocumented internal functionality and doesn't respect category disabling. I made #1398 to serve as an alternative for it.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (ee1849d) to head (14aade7).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1399   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           75        75           
  Lines        13457     13457           
=========================================
  Hits         13457     13457           

☔ 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.

[ahayzen-kdab]

LGTM :-) Good catch on the CStr::from_ptr, and yes those unsafe are not needed probably a misunderstanding how CXX requires unsafe when pointers are used in arguments but it doesn't matter for return types :-)

And yes adding namespaces on the C++ side would be good and that const assert is already on the C++ side and not really checking anything else, so feel free to tidy up in another PR :-)