materialize Update axum and related

As it says on the box, bump axum and related dependencies.

Oct 15 '25 15:10 antiguru

Are these issues resolved? https://github.com/MaterializeInc/materialize/pull/32429

I think yes, as we're not including multiple axum versions anymore. I'll check again to make sure it's true what I'm saying.

Oct 15 '25 18:10 antiguru

Are these issues resolved? https://github.com/MaterializeInc/materialize/pull/32429 I think yes, as we're not including multiple axum versions anymore. I'll check again to make sure it's true what I'm saying.

Turns out I was wrong, console-subscriber pulls in old versions of axum. :(

Oct 16 '25 07:10 antiguru

The problems for cloud are not related to us having multiple versions of axum in our tree, but rather that our crates expose axum types and the cloud repo uses them and expects them to be compatible with their axum dependency.

So this would be a non-issue if we also updated the cloud repo's axum to the same version but we can't because they also have some other dependencies that expect an older version and so the two sets of types can't be combined.

Oct 16 '25 14:10 petrosagg