fix: separate trigger hook lifecycle to prevent missed events on Android

[mfazekas]

Fixes #230

Unstable onTrigger callback references cause useRiveTrigger to silently stop receiving events on Android after re-renders.

useRiveTrigger now manages its own property lifecycle (like useRiveList) instead of going through useRiveProperty. The callback is stored in a ref so its identity doesn't affect native property disposal. useRiveProperty is simplified — the onPropertyEventOverride escape hatch is removed and the options parameter becomes a plain getProperty function.

Root cause and reproducer

Root cause

useDisposableMemo disposes the old native property and creates a new one during the render phase (via ref mutation). When the callback identity changes (e.g. onTrigger without React Compiler memoization), options changes, which triggers this dispose/create cycle.

The problem: if a no-op state update (like setError(null) when error is already null) triggers a re-render that produces identical JSX output, React bails out — it runs the component function but skips the commit and effects. Since useEffect is skipped, the listener is never re-subscribed to the new property.

useDisposableMemo:  deps changed → DISPOSE old, CREATE new   ✅ runs (render phase)
useEffect:          deps changed → should re-subscribe...    ❌ skipped (bailout)

The property is orphaned — disposed old one is dead, new one has no listener. All subsequent trigger events are silently lost.

Reproducer

import { useState } from 'react';
import { View, Text } from 'react-native';
import {
  RiveView, useRiveFile, useRiveTrigger,
  useViewModelInstance, Fit,
} from '@rive-app/react-native';

export default function Issue230() {
  'use no memo'; // disable React Compiler → unstable callbacks

  const [triggerCount, setTriggerCount] = useState(0);
  const { riveFile } = useRiveFile(require('./rewards.riv'));
  const { instance } = useViewModelInstance(riveFile);

  // New reference every render — this is what triggers the bug
  const onTrigger = () => setTriggerCount((c) => c + 1);

  useRiveTrigger('Button/Pressed', instance, { onTrigger });

  return (
    <View>
      <Text>Triggers received: {triggerCount}</Text>
      {riveFile && instance && (
        <RiveView file={riveFile} fit={Fit.Contain} dataBind={instance}
          style={{ width: '100%', height: 200 }} />
      )}
    </View>
  );
}
// Tap the Rive button — first tap works, then triggers stop.
// On Android the trigger fires at the native level (chest opens)
// but the JS callback is never called after the bailout render.