Fix image measure function to apply inherent aspect ratio to style sizes

[nicoburns]

Objective

• Fixes UI: image with Absolute position don't render correctly #13155
• fixes UI Node's transform is sometimes incorrectly calculated #13517
• Supercedes UI: Image fills aspect_ratio of texture dimensions #13381
• Requires Enable correct image measure functions DioxusLabs/taffy#661

Solution

• Taffy has been updated to:
  • Apply size styles to absolutely positioned children
  • Pass the node's Style through to the measure function
• Bevy's image measure function has been updated to make use of this style information

Notes

• This is currently using a git version of Taffy. If this is tested as fixing the issue then we can turn that into a Taffy 0.5 release (this would be the only change between Taffy 0.4 and Taffy 0.5 so upgrading is not expected to be an issue)
• This implementation may not be completely correct. I would have preferred to extend Taffy's gentest infrastructure to handle images and used that to nail down the correct behaviour. But I don't have time for that atm so we'll have to iterate on this in future. This PR at least puts that under Bevy's control.

Testing

• I manually tested the game_menu_example (from UI: image with Absolute position don't render correctly #13155)
• More testing is probably merited

---

Changelog

No changelog should be required as it fixes a regression on main that was not present in bevy 0.13. The changelog for "Taffy upgrade" may want to be changed from 0.4 to 0.5 if this change gets merged.

[nicoburns]

CC @bugsweeper @porkbrain

[alice-i-cecile]

@bugsweeper can I get your review here as well?

[mockersf]

not sure I understand what you mean by this comment

[nicoburns]

When we get to this line we have width: Option<f32> and height: Option<f32>. Applying the aspect ratio means that if one dimension is Some and the other None then it will fill in the none value using the aspect ratio and the value in the other dimension.

[bugsweeper]

This PR contains changes done according to one of previously approved in the issue ways. Looks solid. Examples work correctly. There is only one problem, in this PR bevy_ui depends on personal fork of taffy, it's the best what we can get from changing two separate but dependent crates at same time, but it's not suitable for release. Should we wait some time (two weeks?) for taffy new release?

[nicoburns]

There is only one problem, in this PR bevy_ui depends on personal fork of taffy, it's the best what we can get from changing two separate but dependent crates at same time, but it's not suitable for release. Should we wait some time (two weeks?) for taffy new release?

Me (and Alice) are maintainers of Taffy. I/we can put out a release whenever one is needed, I just don't want to put out a release that doesn't actually fix the problem. The fix looks like it works for #13155 to me, but I was hoping that the proposed fix could get a little more testing, and confirmation from at least one other person that it works first.

[bugsweeper]

Me (and Alice) are maintainers of Taffy

Verry well, I didn't know that.