Add msbuild.json as problem matcher (#603)

[Falco20019]

Description:
Added msbuild.json as seperately owned matched. This makes it possible to disable it seperately. Tests are added and I used it in our CI pipeline already.

Related issue:
#603

Check list:

• Mark if documentation changes are required.
• Mark if tests were added or updated to cover the changes.

[Falco20019]

Anything I could do to help you on gettings this reviewed?

[Falco20019]

Any chance to get this fixed?

[Falco20019]

Ping @aparnajyothi-y @lmvysakh @HarithaVattikuti

[Falco20019]

Another ping as it's 6 months. Just let me know if it's even wanted. If yes, I can rebase and fix conflicts. If no, I can close it.

/CC @priya-kinthali @HarithaVattikuti

[priya-kinthali]

Hello @Falco20019👋,
Thank you for this PR! As mentioned in #603, at this point, we haven't seen enough community demand to prioritise this, but we'll consider exploring the possibility of incorporating these changes in a future update as we gather more community engagement and interest. Thanks again for your contribution!

[lmvysakh]

Hello @Falco20019,

Thank you for your contribution. We have reviewed the PR and wanted to let you know that, the regex currently requires the [project] suffix to be present for a match. However, not all MSBuild error/warning messages may include the project path in brackets. Since audit output legitimately appears in both forms( with and without [project] suffix ), the matcher could be updated to treat the trailing \[...\] group as optional to reliably annotate NuGet audit warnings.

Also could you please take the latest changes from the main branch and resolve the merge conflicts ?

[Falco20019]

I am not using GitHub Actions anymore, so I will drop this. Totally forgot about it after that long time. Might also be covered by #717 that recently got merged.