[LayoutNG] Remove NGConstraintSpace allocation when computing float inline-size.

This shouldn't have any behaviour change. Instead of using the
ComputeInlineSizeForFragment call directly, we optimistically perform layout
on the float to determine this size.

This saves an allocation of an NGConstraintSpace (and simplifies the code
dramatically), which results in a 25% perf increase in some float
benchmarks (see previous pinpoint result).

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: I111e62a4c16c206473085ebd309719f017196959
Bug: 635619
Reviewed-on: https://chromium-review.googlesource.com/1143882
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#576778}
2 files changed