Assert new COS revision created and colliding after upgrade

Check that ${NAME}-2 (the dup's second ClusterObjectSet) exists and
reports collision after upgrading the conflicting extension to v1.0.1.
This proves the upgrade created a new revision and that the higher
revision number doesn't cause object takeover.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: Per G. da Silva

test/e2e/features/update.feature

@@ -310,7 +310,7 @@ Feature: Update ClusterExtension
       revision object collisions
       """
     When ClusterExtension is updated to version "1.0.1"
-    Then ClusterExtension reports Progressing as True with Reason Retrying and Message includes:
+    Then ClusterObjectSet "${NAME}-2" reports Progressing as True with Reason Retrying and Message includes:
       """
       revision object collisions
       """