Test(refactor): clean user created after each scenario

[anon-pradip]

Description

The test suite was encountering 404 status code when running multiple test scenarios due to the userDetails array not being reset after cleanup. This caused subsequent test runs to attempt cleaning up already-deleted resources.

Before: When running multiple test scenarios, the cleanup process would try to delete the same resources multiple times, causing "Resource Not Found" errors

After: Each test scenario now starts with a clean state, preventing duplicate cleanup attempts and making the tests more reliable

Related Issue

• CI failure: https://github.com/JankariTech/web-app-presentation-viewer/actions/runs/17233258895/job/48893162729?pr=108

Motivation and Context

Run multiple tests in future smoothly

How Has This Been Tested?

• test environment:
• locally and CI

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)
• Tests only (no source changes)
• Documentation only (no source changes)
• Maintenance (e.g. dependency updates or tooling)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation updated