Documentation: useInsertMutation - revalidate config

[woof-pawsportal]

Describe the bug
First, thank you for this great project.

If a query contains gte or lte filters, it's unclear that one should use revalidate: true in the config to cause the cache to revalidate. This makes sense that advanced logic like comparing date ranges would not be processable locally, but .eq and other filters will work without revalidate: true.

To Reproduce

    const { data } = useQuery(
        supabase.from('habit_tracking')
            .select('id, timestamp, habit_goal_id')
            .eq('habit_goal_id', id)
            .gte('timestamp', firstDateVisible?.toISODate())
            .lte('timestamp', lastDateVisible?.toISODate())
        ,
        {
            revalidateOnFocus: false,
            revalidateOnReconnect: false,
        }
    );
    console.log(data);
    const { trigger: insert } = useInsertMutation(
        supabase.from('habit_tracking'),
        ['id'],
        'id, timestamp, habit_goal_id',
        {
            onSuccess: () => console.log('fired insert mutation on habit tracking!'),
            // Required for gte and lte in query
            revalidate: true, // If gte & lte filters removed, the cached query is returned with all data
        },

To insert

await insert([{
            timestamp: date.toISO(),
            habit_goal_id: id
        }]);

Expected behavior
Add documentation on what query filters work without revalidate: true in https://github.com/psteinroe/supabase-cache-helpers/blob/main/docs/pages/postgrest/mutations.mdx

Additional context
Wanted to make sure this is expected behaviour before filing PR.

[psteinroe]

Date values should work. So revalidation should not be required. Can you provide a repro?