[Bug] Incorrect Typescript typing for fileRenameFunction

[mooalot]

Is there an existing issue for this?

• I have searched the existing issues

Have you updated FilePond and its plugins?

• I have updated FilePond and its plugins

Describe the bug

Its not super detrimental and is easy to get around, but just thought I'd point it out. The fileRenameFunction is incorrectly typed as per the latest release of FilePond and FilePond Rename plugin.

Current
fileRenameFunction?: | undefined | null | ((options: { basename: string; extension: string; name: string; }) => string) | Promise<string>

What it probably should be
fileRenameFunction?: | undefined | null | ((options: { basename: string; extension: string; name: string; }) => string | Promise<string>);

Reproduction

I don't think its worth creating a sandbox. Steps to reproduce are:

1. Download latest filepond-plugin-file-rename and filepond
2. Make sure you're using typescript in your project
3. Try to set the fileRenameFunction on the filepond options (this is the example in the docs):
   FilePond.setOptions({ fileRenameFunction: (file) => new Promise((resolve) => { resolve(window.prompt('Enter new filename', file.name)); }), });
4. Voila it doesn't work with typescript

Environment

Typescript

[rikschennink]

PR is welcome