fix(modal): make dismiss idempotent when modal is not presented

[janicduplessis]

Motivation

Calling dismiss() on a modal whose status is INITIAL — never presented, or already self-dismissed and reset — permanently breaks it: every subsequent present() silently no-ops. handleDismiss falls through the early-exit and sets statusRef to DISMISSING, nothing ever resets it (no BottomSheet is mounted to fire onClose), and handlePortalRender bails on DISMISSING forever after.

This breaks the common declarative wrapper pattern:

useEffect(() => {
  if (visible) modalRef.current?.present();
  else modalRef.current?.dismiss();
}, [visible]);

A backdrop/swipe close resets the status to INITIAL, so the wrapper's next dismiss() hits exactly this case.

This PR treats INITIAL as already-closed in handleDismiss, mirroring CLOSED/MINIMIZED, so dismiss() is idempotent. Full analysis and a Snack repro are in #2669.

Verified in a real app on iOS after upgrading to 5.2.14: with this change, present → user close → dismiss() → present cycles work repeatedly.

Fixes #2669

Before / after

Minimal repro (scripted): dismiss() on a never-presented modal, then present() twice.

Before — present() never works after the initial dismiss():

upstream-before2.mp4

After — dismiss() is a safe no-op and present() opens the sheet:

upstream-after2.mp4

[github-actions]

This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[janicduplessis]

Not stale

[github-actions]

This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days.