Add problem matchers for deno lint

[r7kamura]

Related to:

• add problem matcher for fmt and lint  #53

I did not add a matcher for deno fmt --check this time, because I thought its output lacked tinformation to be used by problem matchers and could not be handled well.

I have tried this feature on my own sample project and confirmed that it works well like this:

The real example is here:

• Test problem matchers r7kamura/bump-request#12

[r7kamura]

(warning|warn|error)

I know that there is at least an error in the severity of deno lint, but I am not exactly sure what other severities exist. If anyone has exact information, please let me know.

[Keepstacking22]

I don't have a clue of what to do with any of this I'm stuck all the way around if anyone can help me to try and configure this please let me knw thank you

[csvn]

This seems very useful to have included bundled into the denoland/setup-deno action. There's been no activity for half a year now. Any chance for review from the Deno team, @dsherret?

[csvn]

Maybe add deno- as prefix to this file (deno-problem-matchers.json), to make it more consistent with examples from actions/toolkit?

[r7kamura]

Hmmm, it seems to have stopped working properly now. Perhaps the output format of deno lint has changed since I created this pull request?. I will look into it for a while.

---

edit: It seems that the output of deno lint is now flexible depending on the number of digits in the line number where the error exists. I've added support for this as well.

I experimented with the modified version and it worked well, so it probably should not be a problem now.

[crowlKats]

LGTM, sorry for the delay on this. Will cut a release of setup-deno during the day