Update limits for SDXL benchmarks.

[MaheshRavishankar]

This reflects improvements in the compiler for these models.

[geomin12]

Looks good! We are migrating these benchmark tests over to iree-test-suites, so i will also update those values there

[ScottTodd]

Looks good! We are migrating these benchmark tests over to iree-test-suites, so i will also update those values there

Continuing the discussion from #20124 (comment), there should be a single source of truth for such metrics. If we move the source of truth to the test suite repository then workflows running in IREE cannot report failures if those metrics are changed by the code in a pull request.

I've been suggesting we keep the source of truth in this repository for both compilation/run flags (including any extra files like tuning specs) and expected metrics and benchmark results. That means generalizing/parameterizing the test suite so repositories like this one can bring their own configurations without needing to modify the test suite itself, as is already done in the other test suites in that repository like the ONNX op and model test suites.

We can also move the source of truth to a database (not in either repository), so long as we also update the test/benchmark behavior to be advisory ("these benchmark results changed, merging means you accept the new values") and not blocking ("these benchmark results changed, that means the workflow failed").

[benvanik]

(^ yep - if the configs are not in this repo then none of the workflows can block anything in the repo, and they are likely to be in a perpetual red state - for them to be a useful signal to development they must be in the repo so they can be updated along with any commit landing to main that changes the expectations)

[MaheshRavishankar]

Could I get a stamp though @ScottTodd or @geomin12