[full-ci][tests-only] test: run tests in parallel

[anon-pradip]

Description

Problem Statement

Running E2E tests with fullyParallel: true caused failures from two categories of backend conflicts:

1. Resource naming collisions — parallel workers created groups/users/emails with identical names, causing 409 errors and auth mismatches.
2. Verbose world threading — every step/support function accepted and passed world as a parameter, making the code noisy and hard to refactor.

---

Solution

Part 1: Module-Level World Context Store

Replaced parameter threading with a module-level context store (getWorld()/setWorld()). Any function can now access the current worker context without world in its signature.

• world.ts — exports getWorld(), setWorld(), and the World class
• All step files — const world = getWorld() replaces world parameter in every function
• All support functions — getUser, getGroup, getCreatedGroup, getSpace, getCreatedUser etc. call getWorld() internally
• deleteGroup/addUserToGroup — removed the unused world param entirely (already dead)

Part 2: Worker-Aware Resource Isolation

• User emails — unique per worker (alice+w0-abc@example.org) to avoid Keycloak 409 duplicate email errors
• Group display names — (workerIndex) suffix for UI matching
• Spaces/Resources — IDs and names transformed per worker for collision-free parallel execution
• Token auth — logon tries user.id first, falls back to user.originalId for backward compatibility
• Keycloak setup — beforeAll reads directly from store.userStore since no World is available there

---

Backward Compatibility

All transformations are gated on getWorld() returning a valid World instance. Running without parallel workers (fullyParallel: false) bypasses all ID transformations — non-parallel test paths are unaffected.

---

Related Issue

• Fixes [QA] run e2e tests in parallel #13365

Motivation and Context

How Has This Been Tested?

• test environment:
• test case 1:
• test case 2:
• ...

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests
• Documentation
• Maintenance (e.g. dependency updates or tooling)

Open tasks:

• ...

[sonarqubecloud]

Quality Gate failed

Failed conditions
2 Security Hotspots
7.3% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud