docs: ROOM variable naming consistency

docs/src/modules/ROOT/pages/quickstart/shared/constrainttests.adoc

@@ -27,7 +27,7 @@ import ai.timefold.solver.test.api.score.stream.ConstraintVerifier;
 {testannotation}
 class TimetableConstraintProviderTest {
 
-    private static final Room ROOM = new Room("Room1");
+    private static final Room ROOM1 = new Room("Room1");
     private static final Timeslot TIMESLOT1 = new Timeslot(DayOfWeek.MONDAY, LocalTime.of(9,0), LocalTime.NOON);
     private static final Timeslot TIMESLOT2 = new Timeslot(DayOfWeek.TUESDAY, LocalTime.of(9,0), LocalTime.NOON);
 
@@ -100,4 +100,4 @@ So with a constraint weight of `10hard` it would reduce the score by `-10hard`.
 Notice how `ConstraintVerifier` ignores the constraint weight during testing - even
 if those constraint weights are hard coded in the `ConstraintProvider` - because
 constraints weights change regularly before going into production.
-This way, constraint weight tweaking does not break the unit tests.
+This way, constraint weight tweaking does not break the unit tests.