Incorporate GFortran problem matcher definition (when written by user) into the upcoming release

Like it was reported by a different user in https://github.com/microsoft/vscode-makefile-tools/issues/376, I do not see any errors and warnings (which are reported in the terminal window, and are clickable there) in the problems windows.
My configuration is Windows, MSYS2, using gfortran 12.2.0, Visual Studio Code 1.75.1, Makefile tools 0.6.0.

I also see the error in the output terminal which has been reported by several other users (https://github.com/microsoft/vscode-makefile-tools/issues/392):

Error: the task 'makefile: Makefile Tools Build Task' neither specifies a command nor a dependsOn property. The task will be ignored. Its definition is:
{
    "type": "shell",
    "id": "shell,C:\\Programme\\msys64\\ucrt64\\bin\\make.exe,all,-f,C:\\Users\\xxx\\Documents\\Git\\projectname\\_build-gfortran\\subproject\\Makefile,-C,C:\\Users\\jum\\Documents\\Git\\projectname\\_build-gfortran\\subproject,",
    "problemMatcher": [],
    "label": "makefile: Makefile Tools Build Task"
} 

I typically use the icon to build.

I don't know whether it is of importance or not, but I note here the line "problemMatcher": [].

The issue identifies the Makefile Tools Build Task and its empty problemMatcher, with gfortran diagnostics visible in the terminal but not Problems. Start by tracing how that task is created and how problem matchers are selected for user-written gfortran configurations. Done means the diagnostics appear as clickable Problems for the supported configuration.