There is an updated pull request by JamiKettunen against master on the void-packages repository

https://github.com/JamiKettunen/void-packages boost-1.79.0
https://github.com/void-linux/void-packages/pull/36204

boost: update to 1.79.0.b1.
For now I've also dropped the `boost` version from all subpkg names as was previously done for `protobuf` with f38a742bec751aa8c3d9c592e020503256d27a1c, let me know if this should be kept or not; imho maintaining this would be easier if we don't gave versioned pkgnames.

#### Current issues
Cross-compilation fails due to `bjam` building for the host instead of the target:
```
$ ./xbps-src pkg -a aarch64-musl boost
...
=> boost-1.79.0.b1_1: running post-install hook: 06-strip-and-debug-pkgs ...
   Stripped library: /usr/lib/libboost_json.so.1.79.0
   Stripped library: /usr/lib/libboost_nowide.so.1.79.0
/usr/bin/aarch64-linux-musl-strip: Unable to recognise the format of the input file `/destdir/aarch64-linux-musl/boost-1.79.0.b1/usr/bin/bjam'
=> ERROR: boost-1.79.0.b1_1: failed to strip /usr/bin/bjam
=> ERROR: boost-1.79.0.b1_1: post-install_06-strip-and-debug-pkgs: 'find ${PKGDESTDIR} -type f' exited with 1
=> ERROR:   in hook() at common/hooks/post-install/06-strip-and-debug-pkgs.sh:68
=> ERROR:   in run_func() at common/xbps-src/shutils/common.sh:21
=> ERROR:   in run_pkg_hooks() at common/xbps-src/shutils/common.sh:245
=> ERROR:   in main() at common/xbps-src/libexec/xbps-src-doinstall.sh:66
$ file masterdir/destdir/aarch64-linux-musl/boost-jam-1.79.0.b1/usr/bin/bjam 
masterdir/destdir/aarch64-linux-musl/boost-jam-1.79.0.b1/usr/bin/bjam: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=861bc7f944396eb219efdc4e618e58125088d6aa, for GNU/Linux 3.2.0, stripped
```
Additionally a few shared objects aren't built anymore for some reason, namely `libboost_stacktrace_{addr2line,basic,noop}.so.*` & `libboost_fiber.so.*`, so I dropped their subpackages for now (is this ok?).

#### Solved issues
The `failed to install target dependencies! (error 40)` issue was fixed by making new subpackages for `libboost_json.so.*` & `libboost_nowide.so.*`; they were inside the `boost` pkg, depended on `libboost_container` which itself depends on `boost` => circular dependency.

#### Modified patches
`exec_file.patch`: Removed due to being upstream as https://github.com/boostorg/python/commit/d9f06052e28873037db7f98629bce72182a42410
`mips.patch`: Updated to apply on top of https://github.com/boostorg/fiber/commit/5dc9dabc5d5ff8da53ec897c265c9cba1b6ed0df, not sure if this can be removed now(?)

#### To-Do
- Include ~90 commits from `xrevbump 'revbump for boost-1.79.0.b1.' <xrevshlib boost output from master>`

#### Testing the changes
- I tested the changes in this PR: **NO**

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!-- 
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/36204.patch is attached