fix(useFocusVisible): use Object.defineProperty to wrap HTMLElement.prototype.focus

[antododo]

Closes #9649

✅ Pull Request Checklist:

• Included link to corresponding React Spectrum GitHub Issue.
• Added/updated unit tests and storybook for this change (for new code or code which already has tests).
• Filled out test instructions.
• Updated documentation (if it already exists for this component).
• Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

1. yarn jest packages/react-aria/test/interactions/useFocusVisible.test.js — all 18 tests pass, including the new regression test does not throw when HTMLElement.prototype.focus is an accessor-only property.
2. Confirm the regression: temporarily revert just the src/ change, keep the new test, and rerun the command above. The new test should fail with TypeError: Cannot set property focus of [object HTMLElement] which has only a getter. Re-apply the src/ change and the test passes.
3. Smoke-test the wider interactions suite to confirm no regression: yarn jest packages/react-aria/test/interactions/ — all 237 tests pass.
4. In a real browser, nothing should change — focus rings, keyboard vs. pointer modality, and screen-reader virtual focus detection behave identically (the Object.defineProperty call is equivalent to the previous assignment against the default HTMLElement.prototype.focus data descriptor).

🧢 Your Project:

While building components on react-aria-components for Swissquote.ch internal design system where consumers' Jest+JSDOM test suites using @testing-library/user-event's setup() crash on import of any RAC-using component.