fix: troubleshooting.md

[ProximaNova]

Fixed bad markup that I saw at https://docs.ipfs.tech/how-to/troubleshooting/#go-debugging - for example, the command won't run if you try to run it verbatim as it escapes to next line or whatever in Bash/shell:

$ curl localhost:5001/debug/pprof/profile > ipfs.cpuprof`
> 
> ^C
$

BTW, I can't run the Kubo ipfs daemon anymore, it's stuck here for more than an hour

$ ipfs daemon
Initializing daemon... \ Kubo version: 0.30.0
Repo version: 16 \ System version: amd64/linux
Golang version: go1.22.7 \ PeerID: ...
2024/11/17 03:41:29 failed to sufficiently increase receive buffer size
(was: 208 kiB, wanted: 7168 kiB, got: 416 kiB).
See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.

and never reaches "Daemon is ready". Maybe if I update Kubo that will fix it... Restarting the computer and updating to Kubo 0.32.1 mysteriously fixed it. Hope I don't have this problem again!

[welcome]

Thank you for submitting this PR!
A maintainer will be here shortly to review it.
We are super grateful, but we are also overloaded! Help us by making sure that:

• The context for this PR is clear, with relevant discussion, decisions and stakeholders linked/mentioned.
• Your contribution itself is clear (grammar and spelling checked, any code blocks checked and commented) and in its best form. Follow the docs contribution guidelines if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
Next steps:

• A maintainer will triage and assign priority to this PR, commenting on any missing things and potentially assigning a reviewer for high priority items.
• The PR gets reviews, discussed and approvals as needed.
• The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution.
We are very grateful for your contribution!