Fix onSettled call when provided in hook time options

[Madeorsk]

Problem

Fixes #11137
onSettled isn't called anymore when provided in options of useCreate, useDelete and useDeleteMany.

Solution

This is because we define a custom onSettled function when calling useMutationWithMutationMode. The solution is to call onSettled when provided in the options.

How To Test

Here is an example of component that should call onSettled when clicking on the button:

const Example = () => {
    const [settled, setSettled] = useState<string>();
    const [create] = useCreate(
        'foo',
        { data: { bar: 'baz' } },
        { onSettled: () => setSettled('settled') }
    );

    return (
        <>
            <button onClick={() => create()}>Create</button>
            {settled}
        </>
    );
};

Additional Checks

• The PR targets master for a bugfix or a documentation fix, or next for a feature
• The PR includes unit tests (if not possible, describe why)
• The PR includes one or several stories (if not possible, describe why)
• The documentation is up to date

[djhi]

Wouldn't the test code be simpler if you passed a jest.fn to the onSettled option and checked it was called?