glib2: Gio.content_type_guess() changed its signature

[lovetox]

Description / Steps to reproduce the issue

Since a few weeks something changed and we have problems with the Gio.content* methods.

One was fixed here https://github.com/msys2/MINGW-packages/commit/1b141d52378698968de24b53a6f6e13e9eea31af

But there are new problems now with different methods

With the python bindings we see the following error

Gio.content_type_guess() takes exactly 4 arguments (2 given)

although the python binding docs only specify 2 arguments. See https://lazka.github.io/pgi-docs/#Gio-2.0/functions.html#Gio.content_type_guess

I cross posted a issue on the Glib tracker https://gitlab.gnome.org/GNOME/glib/-/issues/3399 but im actually not sure if it is a glib problem.

@Biswa96 it seems you changed something in the glib package regarding GIR, could this be cause because of that?

Expected behavior

Gio.content_type_guess goes back to its old signature

Actual behavior

Gio.content_type_guess has wrong signature

Verification

• [X] I have verified that my MSYS2 is up-to-date before submitting the report (see https://www.msys2.org/docs/updating/)

Windows Version

unknown

MINGW environments affected

• [X] MINGW64
• [ ] MINGW32
• [ ] UCRT64
• [ ] CLANG64
• [ ] CLANG32
• [ ] CLANGARM64

Are you willing to submit a PR?

No response