Is your feature request related to a problem? Please describe.
Currently, bugs found by the schemachange random load roachtest are manually inspected and triaged. Whenever the roachtest fails, new comments are added to #56235, #56230, and #56081. We manually inspect the comments and triage them into the issues in #57470.

Describe the solution you'd like

1. The issues that the roachtest creates are categorized by the run parameters provided by the roachtest. We run the roachtest nightly with 3 sets of params. Roachtest failures (ie. errors/bugs found) are independent of run parameters. It would be ideal if issues were created categorized by the type of error seen. As seen below, the roachtest creates a transaction log in the artifacts directory. Errors can easily be categorized by the expected errors and/or message.
   .

2. The roachtest should not create new comments if we have seen a particular error before. The roachtest runs every night and it would be ideal if we did not get new comments for the same error. This way we won't have to continuously triage failures.

Jira issue: CRDB-3416