test: Changes for catch2 >3.8

[jjerphan]

Description

catch2 3.8 was used but newer versions requires changes, mostly for tests execution as of 3.9.

(The update to catch2 3.12 published yesterday with conda-forge/catch2-feedstock#75 triggered failures on the CI even though other versions between 3.8 and 3.12 have been available for a while on conda-forge.)

Type of Change

• Bugfix
• Feature / enhancement
• CI / Documentation
• Maintenance

Checklist

• My code follows the general style and conventions of the codebase, ensuring consistency
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have run pre-commit run --all locally in the source folder and confirmed that there are no linter errors.
• I have added tests that prove my fix is effective or that my feature works
• New and existing tests pass locally with my changes

[codecov]

Codecov Report

❌ Patch coverage is 47.05882% with 9 lines in your changes missing coverage. Please review.
✅ Project coverage is 63.11%. Comparing base (d9ca597) to head (b368524).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...mamba/tests/libmamba_logging/test_main_logging.cpp	0.00%	7 Missing ⚠️
libmamba/tests/src/test_main.cpp	71.42%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##            main    #4134       +/-   ##
==========================================
+ Coverage   4.19%   63.11%   +58.92%     
==========================================
  Files        315      316        +1     
  Lines      38777    38806       +29     
  Branches    2996     2986       -10     
==========================================
+ Hits        1625    24494    +22869     
+ Misses     37149    14241    -22908     
- Partials       3       71       +68     

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

[Klaim]

LGTM, very minor suggestions below, you can ignore

[Klaim]

LGTM