port to meson cargo

Use the new unstable meson cargo support. This simplifies the
meson.build script and allows to use crates such as clap that require
picking up features from Cargo.toml.

This also allows us to not embed thiserror in subprojects, and instead
use a wrap file with a custom meson.build and some patches to make it
compile without running its build.rs script.

.gitea/workflows/gentoo-utils.yml

@@ -89,7 +89,7 @@ jobs:
       image_tag: ${{ steps.image-changes.outputs.image_tag }}
 
   build:
-    runs-on: gentoo
+    runs-on: brutalisk
     env:
       CC: 'clang'
       CXX: 'clang++'
@@ -108,7 +108,7 @@ jobs:
   # FIXME: Currently this rebuilds everything. Instead we should bring over the build dir from the build job. This will come in handy
   # when we have multiple build targets and configs. What we have currently is fine until we get lots of builds going
   test:
-    runs-on: gentoo
+    runs-on: brutalisk
     env:
       CC: 'clang'
       CXX: 'clang++'
@@ -126,7 +126,7 @@ jobs:
           ninja test -C build
 
   fuzz:
-    runs-on: gentoo
+    runs-on: brutalisk
     env:
       CC: 'clang'
       CXX: 'clang++'
@@ -158,7 +158,7 @@ jobs:
         continue-on-error: true
 
   check-format:
-    runs-on: gentoo
+    runs-on: brutalisk
     needs: [build-oci-image]
     container:
       image: ${{ vars.REGISTRY_URL }}/${{ gitea.repository }}:${{ needs.build-oci-image.outputs.image_tag }}
@@ -173,7 +173,7 @@ jobs:
           ninja rustfmt -C build
 
   docs:
-    runs-on: gentoo
+    runs-on: brutalisk
     needs: [build-oci-image]
     container:
       image: ${{ vars.REGISTRY_URL }}/${{ gitea.repository }}:${{ needs.build-oci-image.outputs.image_tag }}
@@ -187,7 +187,7 @@ jobs:
           ninja rustdoc -C docs
 
   grep:
-    runs-on: gentoo
+    runs-on: brutalisk
     needs: [build-oci-image]
     container:
       image: ${{ vars.REGISTRY_URL }}/${{ gitea.repository }}:${{ needs.build-oci-image.outputs.image_tag }}