[tests] add test and problem report uploading to the server test workflow

[pq]

Adds test and problem report uploading to the dart-analysis-server-tests workflow:

Sample Reports

Tests

Problems

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our [contributor guide](https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Dart contributions to our repos should follow the Dart style guide and use dart format.
• Java and Kotlin contributions should strive to follow Java and Kotlin best practices (discussion).

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[pq]

Hilariously, this last run has no failures, but you can check out the problems report in the uploaded zip here:

https://github.com/flutter/dart-intellij-third-party/actions/runs/19559937926/artifacts/4636302178

[cj-radcliff]

LGTM

[jwren]

If this works, this is great! What does the CLI output look like, i.e. is it discoverable when it is written to these locations? Also, why not add this to to the Jobs?

[pq]

I've been watching runs and it seems to work as intended! 🎉

(For example, this recent run: job/56077860294 generated artifacts here.)

What does the CLI output look like, i.e. is it discoverable when it is written to these locations?

If you squint at the picture above you can see a link is printed in the results. Here it is again:

Also, why not add this to to the Jobs?

You mean add a separate job? What would be the benefit?

(FWIW I did try actually try that initially but hit some snags and couldn't get the upload-artifact action to find the artifacts. I think I understand why after sleeping on it. If there's a good reason to get that working I can take another crack. Just let me know!)