Add problem-matchers to help users

https://github.com/actions/toolkit/blob/master/docs/commands.md#problem-matchers

> Error: error creating GitHub release: POST https://api.github.com/repos/jsoref/ssh-gateway-helm/releases: 422 Validation Failed [{Resource:Release Field:tag_name Code:already_exists Message:}]

With a problem matcher, errors like this are surfaced in a much friendlier way.

without them, one has to open the action log in search of interesting things (i.e. reading the entire log).

With them, you at least get something like this:

And if you do a bit more magic, you could even surface the error to the line that defined the tag in the chart:

---
Filing for now, I might try to implement this later. It bites me regularly.

Start with the linked docs/commands.md problem-matchers section and review how the action currently exposes errors in its logs. Done means release errors such as the tag_name validation failure are surfaced as actionable annotations, potentially pointing to the chart line that defined the tag; no source file or test is named.

Written by the indexing model from the issue text.