Issue template: convert to form and add log instructions for deskop

[Frenzie]

Follow-up to #13632, also see #13619 (comment).

---

This change is 

[Copilot]

Pull Request Overview

This PR updates the bug report issue template by introducing a new form-based template while removing the old markdown-based template.

• Introduces the new .yml template with structured fields including dropdowns, input, and textarea types.
• Removes the old .md template to streamline issue reporting.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
.github/ISSUE_TEMPLATE/bug_report.yml	Added a new structured bug report template form
.github/ISSUE_TEMPLATE/bug_report.md	Removed the legacy markdown bug report template

[mergen3107]

Shouldn't it be tee crash.log?
To make it consistent with all other crash.log files :D (just a thought)

[benoit-pierre]

Do we really want tee -a? IINM, the restart loop is handled inside the script, so I'm not sure appending to the file is a good idea.

[shuvashish76]

Not necessary for other linux packages. But AppImage is an exception as we can run multiple versions of it. I guess it helps to detect which version has crashes/issues? 🤷🏻 Personally I find it useful, instead of moving each new crash.log to a separate location each-time I run KOReader then compare by multiple files in text editor..

[pazos]

In flatpak it is flatpak run rocks.koreader.KOReader 2>&1 | tee crash.log

[Commodore64user]

Do logs get automatically converted to code blocks? And what about spoilers?

edit: i’ll answer my own first question, render: shell so yeah

[Frenzie]

And what about spoilers?

The most obvious alternative is to get rid of the render: shell and prefill it with the old:

<details>
  <summary>crash.log</summary>

```
<Paste crash.log content here>
```
</details>

But maybe paste for small, upload crash.log for large is better anyway. We'll see. It's not set in stone, just an initial conversion.