Add an assertion to IterableSubjectTest#iterableContainsAtLeastInOrde…

…rWithOneShotIterableWrongOrder.

We don't handle printing one shot iterables when the assertion fails,
but previously the test omitted printing the contents of "but was,"
so it seemed like the test was passing by accident.
Adding an explicit assert here to make it clear that the test is passing as intended and a TODO for improving the behavior.

RELNOTES=n/a
PiperOrigin-RevId: 447704700

core/src/test/java/com/google/common/truth/IterableSubjectTest.java

@@ -448,6 +448,7 @@ public String toString() {
  "expected order for required elements",
  "but was");
  assertFailureValue("expected order for required elements", "[1, 3, null]");
+ assertFailureValue("but was", "BadIterable"); // TODO(b/231966021): Output its elements.
  }
 
  @Test