GitHub CI: Run memory profiling with valgrind on Linux and FreeBSD

[rdmark]

Use the built-in valgrind wrapper in Meson to run memory profiling in the CI pipeline

It might be possible to use valgrind on other platforms than Linux and FreeBSD, but these two were the ones that worked out of the box

[rdmark]

@msteinert any other parameter apart from --leak-check=full --error-exitcode=1 to make the Meson wrapper run the same tests as your automake wrapper?

For the record, I was able to get the valgrind wrapper up and running on Solaris on OmniOS as well, but it is reporting leaks. More analysis required before turning it on in the pipeline.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[msteinert]

This is great! I think we may want to consider dropping Autotools at some point now...

[rdmark]

The only user of Autotools that I know of is the YACP project. (A Cygwin package repo.)

https://github.com/fd00/yacp/tree/master/bstring

How about we can keep Autotools in the next stable release but flag in the release notes that it will be removed in the subsequent release?

[msteinert]

Sounds like a good plan.

I recognize the most recent contributor to that package...

[rdmark]

Right, I leaned in to get the package bumped from 1.0.0 to 1.0.1.

I had never used YACP before, but it was flagged by Repology: https://repology.org/project/bstring/versions