Fix boost spirit and add mqtt5

[martin4861]

• Add textual header include/boost/spirit/home/x3/nonterminal/detail/rule.hpp to boost.spirit
• Add boost.mqtt5

[bazel-io]

Hello @wep21, @Vertexwahn, modules you maintain (boost.spirit) have been updated in this PR.
Please review the changes. You can view a diff against the previous version in the "Generate module diff" check.

[bazel-io]

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (boost.mqtt5) have been updated in this PR.
Please review the changes. You can view a diff against the previous version in the "Generate module diff" check.

[gemini-code-assist]

Code Review

This pull request introduces the boost.mqtt5 module and provides a fix for boost.spirit by adding a new version. While the structure and intent are mostly correct, there are a couple of critical copy-paste errors in the MODULE.bazel files within the overlays. Specifically, boost.mqtt5's MODULE.bazel is incorrectly copied from boost.math, and boost.spirit's MODULE.bazel has an outdated version string. These issues must be fixed for the modules to be correctly resolved by Bazel.

[wep21]

@bazel-io skip_check unstable_url

[wep21]

@martin4861 Please update integrity with

bazelisk run //tools:update_integrity -- boost.spirit --version 1.89.0.bcr.2

[martin4861]

@martin4861 Please update integrity with

bazelisk run //tools:update_integrity -- boost.spirit --version 1.89.0.bcr.2

@wep21 Done! How are boost versions usually released? I only created mqtt5 and spirit for 1.89.0.bcr.2, but for other versions all boost modules have been created.

[wep21]

@fmeum @meteorcloudy please add presubmit auto run tag.

[wep21]

I'm not sure about the current status of this PR.
#6530

@fmeum @kgreenek Is it better to wait for the PR merged?

[martin4861]

@bazel-io skip_check incompatible_flags

[kgreenek]

I'm not sure about the current status of this PR. #6530

@fmeum @kgreenek Is it better to wait for the PR merged?

That other PR should hopefully get merged in the next day or two, so if you can wait that would probably be the easiest.

It is expected now (as of recently) that a new bcr version for all the other boost submodules should be generated whenever one is updated. That is done by running python3 modules/boost/add_boost_version.py <version>

There is an ongoing discussion happening about that PR and its implications here: #6511