fix(overlay): remove nonexistent OverlayDialog export

[kwy404]

Description

The exports map in @spectrum-web-components/overlay lists ./src/OverlayDialog.js, but there is no OverlayDialog source file in the package, so that path can never resolve. This removes the stale entry.

Motivation and context

Tooling that reads the exports map, and consumers browsing it, are pointed at a module that does not exist.

Related issue(s)

• fixes [Bug]: OverlayDialog is being exported even though it doesn't exist #5659

Screenshots (if appropriate)

---

Author's checklist

• I have read the CONTRIBUTING and PULL_REQUESTS documents.
• I have reviewed at the Accessibility Practices for this feature, see: Aria Practices
• I have added automated tests to cover my changes.
• I have included a well-written changeset if my change needs to be published.
• I have included updated documentation if my change required it.

---

Reviewer's checklist

• Includes a Github Issue with appropriate flag or Jira ticket number without a link
• Includes thoughtfully written changeset if changes suggested include patch, minor, or major features
• Automated tests cover all use cases and follow best practices for writing
• Validated on all supported browsers
• All VRTs are approved before the author can update Golden Hash

Manual review test cases

• Exports map only lists existing files
  1. Run yarn build in 1st-gen
  2. Check that every path in the exports field of 1st-gen/packages/overlay/package.json exists in the package
  3. Expect no OverlayDialog entry and no missing files

Device review

• Did it pass in Desktop?
• Did it pass in (emulated) Mobile?
• Did it pass in (emulated) iPad?

Accessibility testing checklist

Not applicable: this only changes the package exports map and has no runtime or UI effect.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 299559b

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.

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

[coveralls]

Coverage Report for CI Build 35983490584

Warning

No base build found for commit f9d5366 on main.
Coverage changes can't be calculated without a base build.
If a base build is processing, this comment will update automatically when it completes.

Coverage: 96.291%

Details

• Patch coverage: No coverable lines changed in this PR.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

Requires a base build to compare against. How to fix this →

---

Coverage Stats

Relevant Lines:	39853
Covered Lines:	38574
Line Coverage:	96.79%
Relevant Branches:	6572
Covered Branches:	6129
Branch Coverage:	93.26%
Branches in Coverage %:	Yes
Coverage Strength:	461.95 hits per line

---

💛 - Coveralls

[rubencarvalho]

Thank you so much for this fix, @kwy404! 🙏
Our CI can't use repository secrets on PRs from forks yet, so some required checks can't run here. To get this merged, we moved your change to an internal PR: #6794. Your commit is carried over unchanged, and you're still its author, so you keep full credit.

We'll close this PR in favor of #6794 . Thanks again for contributing!