Issue number:resolves#30449

What is the current behavior?

Wheel scrolling inside ion-datetime does not provide host-level lifecycle events for app code to react to start/end of scrolling.

What is the new behavior?

• ion-datetime re-emits wheel scroll lifecycle events from inner columns:
  • ionScrollStart when any wheel column begins scrolling.
  • ionScrollEnd once all active columns settle, coalesced with a 300ms debounce.
  • Events do not bubble to avoid duplicate handling; they are emitted on the host.
• ion-picker-column emits ionScrollStart and ionScrollEnd at scroll start/end.
• API/types updated to expose the new events across frameworks (Angular/Vue proxies).

Does this introduce a breaking change?

• Yes
• No

Other information

• core/src/components/datetime/datetime.tsx: capture-phase listeners, coalescing logic, new events
• core/src/components/picker-column/picker-column.tsx: emits start/end at scroll boundaries
• core/src/components/datetime/test/prefer-wheel/datetime.spec.ts: replace fake timers with explicit waits
• core/api.txt, core/src/components.d.ts, Angular/Vue proxies: API surface/types for new events
• Proxy changes are generated to reflect the new events(updated during the build).

Verification

• Targeted specs: cd core && npm ci && npm run test.spec -- src/components/datetime/test/prefer-wheel/datetime.spec.ts (expect 3 passed).

• Manual: cd core && npm start, open /src/components/datetime/test/prefer-wheel/index.html.

Scroll a wheel column: app receives one ionScrollStart at the beginning, one ionScrollEnd after settling.