[HACK Week] Attach connectivity test log to Zendesk issue

[adborbas]

This is a follow-up on HACK Week: Add details for decoding errors in troubleshooting tool

Description

This PR attaches the troubleshooting tool's output as an attachment to the Zendesk issue if you navigate to the Contact Support page.

• I've updated ZendeskManager to support updating multiple attachments.
• Improved the sizing of the icon on the Troubleshooting Connection screen.
• Updated ConnectivityToolViewModel to include the technical details section for generic errors.

Test Steps

⚠️ This is an E2E test. You'll need to resolve the opened issue in Zendesk.

1. Download the app from the build. You need the PR build as it contains the keys for creating the request.
2. Login with any store.
3. Navigate to Settings/Troubleshooting Connection/
4. [Optional] You can mock any of the network response to fail to see a more detailed report.
5. Wait for the report to finish.
6. Tap Contact Support
   7 . Fill out required fields.
7. Tap "Submit Support Request"
8. Open Zendesk and locate the issue.
9. Validate that logs are attached.
10. Download and the connectivitytest_log attachment and check it.

Screenshots

Before	After

---

• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

[dangermattic]

	1 Warning
⚠️	This PR is assigned to the milestone 23.9. This milestone is due in less than 2 days. Please make sure to get it merged by then or assign it to a milestone with a later deadline.

Generated by 🚫 Danger

[wpmobilebot]

📲 You can test the changes from this Pull Request in WooCommerce iOS Prototype by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce iOS Prototype
	Build Number	pr16449-6db510c
	Version	23.8
	Bundle ID	com.automattic.alpha.woocommerce
	Commit	6db510c
	Installation URL	1tep06qagf7ho

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[itsmeichigo]

Thanks for working on this! I tested both the happy path and an edge case - I have a question regarding the edge case below 👇

[itsmeichigo]

I tested an edge case:

• Run the tests and stub one of the request to fail with decoding error.
• Retry the same test but let it succeed.
• Result: I see both failure and success in the log:

## 1. Internet Connection
Took: 0ms
Result: Success
## 2. Connecting to WordPress.com Servers
Took: 721ms
Result: Success
## 3. Connecting to your site
Took: 1567ms
Result: Success
## 4. Fetching your site orders
Took: 1940ms
Result: Success
## 5. Fetching products in your store
Took: 12208ms
Result: Operation: Fetching products in your store
Error Type: Decoding Error

Issue: Required Key Not Found
Missing Key: id
Coding Path: data → Index 0
Description: No value associated with key CodingKeys(stringValue: "id", intValue: nil) ("id").
## 6. Fetching products in your store
Took: 1756ms
Result: Success

[adborbas]

Thanks for pointing this out. I've intentionally decided to keep every "test run" and not overwrite the original run when retrying a test. This way, we can see the full picture and not just the last "snapshot". And since we are attaching the report, the report size is not a constraint.

Would you prefer overwriting with the retry?

[itsmeichigo]

Yeah I have mixed feelings about this but it might not be straightforward to replace the results. Sometimes intermittent failures are also a sign of something broken on a site. Let's keep this for now then.

[itsmeichigo]

We can simply use testCase.title for this.

[adborbas]

From a technical point of view, yes, we could. But testCase.title is localized, so the HEs would have to translate it to see which step it was. We are making sure the report will have English titles by using caseName here.

[itsmeichigo]

Approving as the comments above are not blocking.