feat: add Report an issue screen

[maparr]

It closes #931

[brusherru]

In the rest, it sends reports to the Sentry, so it works and this is already great!
Let's polish it a little bit and merge :)

[github-actions]

Compiled Binaries

• Windows: https://storage.googleapis.com/smapp/pr-e61e762ea8babc853bb145ec8eb4e3001b9677e7/Spacemesh%20Setup%200.2.6-pr.941.exe
• macOS: https://storage.googleapis.com/smapp/pr-e61e762ea8babc853bb145ec8eb4e3001b9677e7/Spacemesh-0.2.6-pr.941.dmg
• Linux: https://storage.googleapis.com/smapp/pr-e61e762ea8babc853bb145ec8eb4e3001b9677e7/spacemesh_app_0.2.6-pr.941_amd64.deb

[github-actions]

Compiled Binaries

• Windows: https://storage.googleapis.com/smapp/pr-3885ce2db7ebf6c19e04f1d2c097e1da080c5dc8/Spacemesh%20Setup%200.2.6-pr.941.exe
• macOS: https://storage.googleapis.com/smapp/pr-3885ce2db7ebf6c19e04f1d2c097e1da080c5dc8/Spacemesh-0.2.6-pr.941.dmg
• Linux: https://storage.googleapis.com/smapp/pr-3885ce2db7ebf6c19e04f1d2c097e1da080c5dc8/spacemesh_app_0.2.6-pr.941_amd64.deb

[github-actions]

Compiled Binaries

• Windows: https://storage.googleapis.com/smapp/pr-386d262ba4917c00a2a6be8b6f416956133aa01d/Spacemesh%20Setup%200.2.6-pr.941.exe
• macOS: https://storage.googleapis.com/smapp/pr-386d262ba4917c00a2a6be8b6f416956133aa01d/Spacemesh-0.2.6-pr.941.dmg
• Linux: https://storage.googleapis.com/smapp/pr-386d262ba4917c00a2a6be8b6f416956133aa01d/spacemesh_app_0.2.6-pr.941_amd64.deb

[brusherru]

It still collects all the bug reports under the same event in Sentry.
Can we distinct them somehow into different events? 🤔

Mb we can just get rid of eventId in options and let Sentry generate it? 🤔

[maparr]

@brusherru , I checked this moment, seems like because the info that we're sending from 1 computer and 1 env, is similar to what we are sending again and again. In User Feedback category, we will be having different right now

but unfortunately for event , all User Feedbacks will be grouped

so, because User Feedback for Sentry is different from what we are expecting to see in his admin panel, that's why we have a misunderstanding. The main goal I think to see all these issues and react to them.

[oriya]

Is there anyway (must be) for this category to be sent as an email notification to a specific email?
We currently handle all "tech support" via Discord and an email address.
We gonna need current "tech support" to be able to get these notifications.
Alternatively, I guess we can give current tech-support access to Sentry and teach them to look for this grouping.
Thoughts / ideas?

[github-actions]

Compiled Binaries

• Windows: https://storage.googleapis.com/smapp/pr-aab9cf1b70c7aad06566b6e88b1d17fcadb84fb2/Spacemesh%20Setup%200.2.6-pr.941.exe
• macOS: https://storage.googleapis.com/smapp/pr-aab9cf1b70c7aad06566b6e88b1d17fcadb84fb2/Spacemesh-0.2.6-pr.941.dmg
• Linux: https://storage.googleapis.com/smapp/pr-aab9cf1b70c7aad06566b6e88b1d17fcadb84fb2/spacemesh_app_0.2.6-pr.941_amd64.deb

[maparr]

@oriya , let me check how can I configure this pipeline so, discord + email or just email will be ok for us?

[oriya]

email should be fine :) and thank you!

[github-actions]

Compiled Binaries

• Windows: https://storage.googleapis.com/smapp/pr-0bf7c85e66d5a5819ca92e11cefbbb6e9a4e037a/Spacemesh%20Setup%200.2.6-pr.941.exe
• macOS: https://storage.googleapis.com/smapp/pr-0bf7c85e66d5a5819ca92e11cefbbb6e9a4e037a/Spacemesh-0.2.6-pr.941.dmg
• Linux: https://storage.googleapis.com/smapp/pr-0bf7c85e66d5a5819ca92e11cefbbb6e9a4e037a/spacemesh_app_0.2.6-pr.941_amd64.deb

[github-actions]

Compiled Binaries

• Windows: https://storage.googleapis.com/smapp/pr-c145a39516e887e795f851035ef5d523b63a22e9/Spacemesh%20Setup%200.2.6-pr.941.exe
• macOS: https://storage.googleapis.com/smapp/pr-c145a39516e887e795f851035ef5d523b63a22e9/Spacemesh-0.2.6-pr.941.dmg
• Linux: https://storage.googleapis.com/smapp/pr-c145a39516e887e795f851035ef5d523b63a22e9/spacemesh_app_0.2.6-pr.941_amd64.deb

[maparr]

Hey @brusherru , the last changes have already been approved by @oriya, so what we have

1. Client can send unique feedback only once by version ( it is called a fingerprint, it is how the Sentry identifies unique/not unique errors )
2. Other events and messages grouped into 1 for this client
3. Added Alert tracker, that finds new events with the specific match by event/message content, and I'm sending it to our support team where they can find any information.

4. For Other events I will be sending personal once a week or two, because, for duplicate events and messages I cannot define this alert, Sentry doesn't have such an event, on every event update 5. Cleaned up Sentry issues and grouped it, right now we have only a few issues that need to check, a few of them are Windows, that issue on which u working right now

[brusherru]

LGTM