stm32 i2cv1 async regression, silently reads back 0xFF

[MabezDev]

Will need to do a bisect to find the offending commit, but essentially somewhere between the crates.io release and current main there is a regression where i2c doesn't fail it just reads back 0xFF. This was produced on an F2 board, but it more than likely applies to other chips with i2cv1.

Blocking of course works fine.

[jamesmunns]

Might want to reference some of the PRs mentioned here: https://github.com/embassy-rs/embassy/issues/2372

[SpencerSharkey]

i'm seeing the same behavior with i2cv2. blocking works, async doesn't- but only for pmbus devices in my experience so far