fix(test): use unique bridge names and relaxed count assertions (#21966)

* fix(test): use unique bridge names and relaxed count assertions

TestORM_UpdateBridgeType used a hardcoded "UniqueName" and asserted
the global bridge count was exactly 1. With shared DB state from
parallel tests or -count=N, the global count includes other bridges.

Use UUID-based names and assert >= 1 instead of exact count. Verify
deletion by checking the specific bridge is not found.

Fixes: CORE-2391

* fix(test): drop global count assertion, verify specific bridge only

The GreaterOrEqual count check was still fragile. The test only needs
to verify its own bridge exists and can be deleted — not count how
many bridges exist globally.

Fixes: CORE-2391

* fix(test): restore exact count assertions with UUID bridge names

The txdb wrapper should provide per-test transaction isolation, so
exact count assertions are valid. Restore them — if CI fails, the
real bug is broken DB isolation, not the test.

The only change from the original test is UUID-based bridge names
to avoid hardcoded "UniqueName" collisions.

Fixes: CORE-2391

Author: Fletch153

core/bridges/orm_test.go

@@ -107,8 +107,9 @@ func TestORM_UpdateBridgeType(t *testing.T) {
 	ctx := testutils.Context(t)
 	_, orm := setupORM(t)
 
+	bridgeName := bridges.BridgeName("bridge-" + uuid.New().String()[:8])
 	firstBridge := &bridges.BridgeType{
-		Name: "UniqueName",
+		Name: bridgeName,
 		URL:  cltest.WebURL(t, "http:/oneurl.com"),
 	}
 
@@ -120,7 +121,7 @@ func TestORM_UpdateBridgeType(t *testing.T) {
 
 	require.NoError(t, orm.UpdateBridgeType(ctx, firstBridge, updateBridge))
 
-	foundbridge, err := orm.FindBridge(ctx, "UniqueName")
+	foundbridge, err := orm.FindBridge(ctx, bridgeName)
 	require.NoError(t, err)
 	require.Equal(t, updateBridge.URL, foundbridge.URL)