fix(FocusTrap): resolve aria_hidden_nontabbable accessibility violation

[Aryan3902]

Fix #8365

The Issue

The focus guard elements (the hidden spans used to trap focus) were rendered with conflicting attributes: tabIndex="0" combined with aria-hidden="true" and role="presentation".

Reason

A focusable element (tabIndex="0") cannot be marked as hidden (aria-hidden="true") because it creates a state where focus lands on an element that technically "doesn't exist" in the accessibility tree.

The Fix

I have removed aria-hidden={true} and role={'presentation'} from the createFocusableElement helper.

These elements are technically focusable, so they must be exposed to the accessibility tree.

They remain visually hidden via the existing p-hidden-accessible CSS class.

The onFocus event handlers continue to function correctly, redirecting focus instantly without negatively impacting screen reader announcements.

How Has This Been Tested?

Automated Scan: Verified that the aria_hidden_nontabbable (Fail_1) error no longer appears in accessibility scans.

Functional Test: Verified that the focus trap still functions correctly (Focus loops back to the start when tabbing past the last element, and vice versa).

Visual Test: Confirmed no visual regression (the spans remain invisible).

[melloware]

it lokos like Primevue is doing the same thing: https://github.com/primefaces/primevue/blob/b83794d8f989321bd70196d9dd6b0e8cdeef547b/packages/primevue/src/focustrap/FocusTrap.js#L99-L108

[melloware]

Assigned to @tugcekucukoglu to review since PrimeVue is doing the same thing