Fix update_record_files_async signature

[ZedThree]

❤️ Thank you for your contribution!

Description

Trying to upload files via the REST API gives the following (abridged) error:

...
  File "example/venv/lib64/python3.10/site-packages/invenio_files_rest/views.py", line 625, in create_object
    file_uploaded.send(current_app._get_current_object(), obj=obj)
  File "example/venv/lib64/python3.10/site-packages/blinker/base.py", line 266, in send
    return [(receiver, receiver(sender, **kwargs))
  File "example/venv/lib64/python3.10/site-packages/blinker/base.py", line 266, in <listcomp>
    return [(receiver, receiver(sender, **kwargs))
TypeError: update_record_files_async() got an unexpected keyword argument 'obj'

From this, I gather that update_records_files_async requires two arguments, one of which is called obj. It currently takes one argument which is named object_version. With this change it seems to work at least. I'm not sure how to test it automatically though

Checklist

Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

• I'm aware of the code of conduct.
• I've created logical separate commits and followed the commit message format.
• I've added relevant test cases.
• I've added relevant documentation.
• I've marked translation strings (for relevant code).
• I've followed the CSS/JS and React guidelines (for relevant code).
• I've followed the web accessibility guidelines (for relevant code).
• I've followed the user interface guidelines (for relevant code).
• I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
• I've NOT included third-party code (copy/pasted source code or new dependencies).

Third-party code

If you've added third-party code (copy/pasted or new dependencies), please reach out to an architect.

Reminder

By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

1. You license your contribution under the same terms as the current repository’s license.
2. You agree that you have the right to license your contribution under the current repository’s license.