chore: add portal context with comprehensive tests

[Copilot]

Closes #

This PR adds PortalContext functionality to the Portal component and includes comprehensive test coverage to ensure proper behavior.

Changes Made

• PortalContext Integration: Fixed useContext hook call in Portal component to be at component level instead of inside useLayoutEffect (following React hooks rules)
• Enhanced Portal Logic: Updated Portal logic to ensure default portal is created when using default container name from context
• Comprehensive Test Coverage: Added tests to verify:
  • Elements render correctly inside custom Portal when PortalContext is supplied with portalContainerName
  • Elements render in default portal when PortalContext doesn't specify portalContainerName
  • Elements render in default portal when PortalContext portalContainerName is undefined
  • Portal containerName prop correctly overrides PortalContext portalContainerName

Changelog

New

• Added comprehensive test coverage for PortalContext functionality

Changed

• Fixed Portal component hook usage to follow React rules of hooks
• Enhanced Portal default container logic for better context integration

Removed

Rollout strategy

• Patch release
• Minor release
• Major release; if selected, include a written rollout or migration plan
• None; if selected, include a brief description as to why

Testing & Reviewing

All Portal tests are now passing (9/9) including the new comprehensive test coverage for PortalContext functionality.

Merge checklist

• Added/updated tests
• Added/updated documentation
• Added/updated previews (Storybook)
• Changes are SSR compatible
• Tested in Chrome
• Tested in Firefox
• Tested in Safari
• Tested in Edge
• (GitHub staff only) Integration tests pass at github/github (Learn more about how to run integration tests)

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 288b4e3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

👋 Hi, this pull request contains changes to the source code that github/github depends on. If you are GitHub staff, we recommend testing these changes with github/github using the integration workflow. Thanks!