sdk: getMessageStatus is returning wrong message status for finalized withdrawals

[roninjin10]

Describe the bug

Reported in #5983

I've been able to manually finalize withdrawals locally but I don't see the status updated in the SDK's getMessageStatus method

Example L2 withdrawal:

https://optimistic.etherscan.io/tx/0xda9e9c8dfc7718bc1499e1e64d8df6cddbabc46e819475a6c755db286a41b9fa
L1 finalization:

https://etherscan.io/tx/0x9bc7b3a1056d4a2829ea253e290877fb25d61f07153b638767d2bb8d44e520d3
Perhaps because these are pre-bedrock?

I've confirmed that these errors are only showing up on pre bedrock withdrawal. I have yet to finalize a post bedrock withdrawal yet so I will know soon

To Reproduce
Call getMessageStatus with any historical withdrawal on goerli or mainnet

Expected behavior
FInalized withdrawals should find a RelayedMessage event

Additional context
Add any other context about the problem here.

The issue here is we are for some reason hashing the withdrawal is wrong. This will be quicker to debug on a devnet