It looks like the problem there is that the upstream maintainers are not yet willing to accept the pull request that would port the package to ros2. The solutions I can think of would be:
People who want to use christian-rauch’s branch can build from source (which seems to be what is currently happening)
Upstream maintainers could change their minds, merging in the code and then doing the ROS2 release process
End-users could create their own .deb from source, which can be installed to whatever robots need the package
Given that this is such a different set of code than what is currently in the repo, it would be reasonable for christian-rauch to release their own code via the ROS2 release process under its own repository (this may be the best option)