merge_pr_48597

[@container] Correctly match snapped on container-type changes

Unlike for stuck queries, the snapshot client for snapped queries may
outlive a ContainerQueryEvaluator. If a container-type:scroll-state
which is snapped changes its container-type to 'none' and then back
again we may have a snapped state snapshot that does not need an update
when we re-create the ContainerQueryEvaluator.

Make sure the ContainerQueryEvaluator initializes the ContainerValues
with the snapshot state for snapped queries.

Added a test for the stuck feature to verify that works.

Bug: 40279568
Change-Id: I7ced76e4004e9ab7338c6b75b61fe88215438ff7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5926649
Reviewed-by: Anders Hartvoll Ruud [email protected]
Commit-Queue: Rune Lillesveen [email protected]
Cr-Commit-Position: refs/heads/main@{#1368471}