feat: Add error submitter for user feedback

[pablomxnl]

Closes #591

It uses an issue template form, on the yaml, projects list is optional.

When the user clicks the Create GitHub Issue button the browser is launched and takes away the focus of the IDE.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[angelozerr]

Thanks so much!

@fbricon what do you think?

[fbricon]

I'm worried this will potentially generate plenty of duplicate issues as it won't force users to check for existing issues

[pablomxnl]

I'm worried this will potentially generate plenty of duplicate issues as it won't force users to check for existing issues

Understandable, for my plugins I send these errors to sentry . Perhaps maybe it would be better to capture these errors through the telemetry plugin.

[angelozerr]

I wonder if when the issue is created we could check that a similar issue (same title) exists?

[pablomxnl]

I wonder if when the issue is created we could check that a similar issue (same title) exists?

Probably using the gh api, but then would have to deal with tokens in PasswordSafe, as far as I know there is no way to configure GitHub issue workflow to search while/before creating (GitLab does it this way)

this is how the issue form would look like btw

this is how GitLab display similar issues on the issue creation screen:

Another option could be use a webhook on issue opened and search for similar issues and mark duplicates

[fbricon]

according to https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28#primary-rate-limit-for-unauthenticated-users:

The primary rate limit for unauthenticated requests is 60 requests per hour.

That should be more than enough for error reporting, if you cache search results for a given problem, so no need to manage tokens

[pablomxnl]

interesting!!, will take a look.
I see retrofit is available as transitive dependency from the telemetry plugin,
would be ok to use that or add the dependency explicitly ??