Improve description collection for the GDK report

Overview

Currently, the report command automatically gathers a lot of data and copies it to the clipboard. Included in the report is a section to provide a description of the problem <!-- Please add a description of the issue you are facing -->. This is oftentimes missed by users, leading to issues created that contain information about the system but not about the ongoing issue.
In order to improve the troubleshooting experience, a better way of capturing the problem of the reporting user should be found.

Impacted categories

The following categories relate to this issue:

• gdk-reliability - e.g. When a GDK action fails to complete.
• gdk-usability - e.g. Improvements or suggestions around how the GDK functions.
• gdk-performance - e.g. When a GDK action is slow or times out.

Steps to replicate

1. Run gdk report.
2. Ensure that reporting a problem is enforced or very visible.

Proposal

One of the following:

1. Move the hint for the user to describe their issue to the description of the issue to be created.
2. Add a prompt asking for a description of the issue before opening the browser and including the provided description in the report.