Updating issue templates again for rustbot

[xFrednet]

It turns out that our current issue template can sometimes trigger a rustbot error message, as can be seen in #7626. I originally tested this in #7599, but it's apparently a bit inconsistent. This PR adds backticks to the commands, as correctly suggested by @mikerite in the comments. (Thank you!)

@rustbot label +S-blocked

---

Now I also pushed a tiny link fix as well. 🙃

---

changelog: none

[rust-highfive]

r? @llogiq

(rust-highfive has picked a reviewer for you, use r? to override)

[ghost]

Why not surround the whole commad in backticks? I'm sure people will know to remove them.

Or does that have the same issue?

[xFrednet]

The issue is that GitHub ignores backticks inside comments. At least rustbot still triggers with them. I'll ping you inside an HTML comment with backticks as an example

[xFrednet]

Well now it's somehow not triggering rustbot with the backticks. Maybe I missed that in my tests earlier

[xFrednet]

You're right, nice catch! Thank you!

[llogiq]

From my side, this looks Ok. r=me if you think it's ready to merge.

[xFrednet]

@bors r=llogiq

[bors]

📌 Commit 169aea6 has been approved by llogiq

[bors]

⌛ Testing commit 169aea6 with merge df7e63b...

[bors]

☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test
Approved by: llogiq
Pushing df7e63b to master...