First stab at refactoring to use the new built in artifact-url output

[acoffman]

Hi @cansavvy,

I was working on porting the code here: https://github.com/orgs/community/discussions/51403#discussioncomment-5515349 to a generic, reusable action which led me to reading the docs for actions/upload-artifact as the version listed in the discussion answer is deprecated.

It turns out that, based on the release notes and the documented outputs, the artifact URL is now available directly as an output of the upload-artifact action.

This PR is a first stab at refactoring your refactor (in #44) to utilize this fact.

Now the primary action handles generating the reports, uploading them as artifacts, and managing the comments all in one workflow. There shouldn't be a need for the secondary commenter workflow or the API manipulation any longer.

Let me know if you think this makes sense and is the proper direction to take this workflow. If so, I need to do some more cleanup and testing and can go ahead and update the docs as part of this PR as well. (I just didn't want to go too far down this road if you think its the wrong way).

[cansavvy]

This looks great! Thanks for getting this going. So glad to hear they've added this functionality! Let's make this something we can test!