fix(e2e/ontology): add idempotency guard for E2E custom relation type

Mirrors the Cardinality class double-call pattern: a concurrent worker
issuing a stale PUT between addRelationTypesWithCardinality and the term
patches can silently drop CUSTOM_OWNS_RELATION from the global config.
The second (idempotent) call re-asserts the type before term patches run.

Also switches from addRelationTypeWithCardinality (singular) to the batch
variant addRelationTypesWithCardinality so the retry loop and verification
step are the same as Cardinality.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: anuj-kumary

openmetadata-ui/src/main/resources/ui/playwright/support/entity/OntologyExplorerDataClass.ts

@@ -12,7 +12,6 @@
  */
 import { APIRequestContext } from '@playwright/test';
 import {
-  addRelationTypeWithCardinality,
   addRelationTypesWithCardinality,
   addTermRelation,
 } from '../../utils/ontologyExplorer';
@@ -45,11 +44,18 @@ export class OntologyExplorerE2EData {
       this.termBrand.create(apiContext),
     ]);
 
-    await addRelationTypeWithCardinality(apiContext, {
-      name: this.CUSTOM_OWNS_RELATION,
-      displayName: 'GP Owns',
-      cardinality: 'ONE_TO_MANY',
-    });
+    // Use the batch variant so the idempotency guard (double-call) is available.
+    // A concurrent worker that issues a stale PUT between setup and the term
+    // patches below can silently drop this type; the second call re-asserts it.
+    const E2E_CUSTOM_TYPE = [
+      {
+        name: this.CUSTOM_OWNS_RELATION,
+        displayName: 'GP Owns',
+        cardinality: 'ONE_TO_MANY',
+      },
+    ];
+    await addRelationTypesWithCardinality(apiContext, E2E_CUSTOM_TYPE);
+    await addRelationTypesWithCardinality(apiContext, E2E_CUSTOM_TYPE);
 
     // termProduct is patched twice (partOf termCategory, relatedTo termBrand)
     // so these must remain sequential to avoid a PATCH race.