fix: Update instructions for raising support issues

[AboveHero]

• Removed old image assets
• Added new image asset
• Updated documentation
• General semantic changes

This PR will bring the documentation up to date with the new Service Center portal design, and also includes some general semantic improvements.

[AboveHero]

I had no other way of getting the formatting to render correctly than to abuse the formatting of the documentation. I have spent hours trying to get this right, but my conclusion is that the markdownlinter simply does not account for the mkdocs rendering engine. When formatting these unordered lists in a traditional markdown format they render as flat rather than nested unordered lists.

$ tox -e markdownlint 
markdownlint: commands[0]> pymarkdown -c .pymarkdown.json scan -r docs
docs/howto/support/raise-issues.md:46:5: MD007: Unordered list indentation [Expected: 2, Actual=4] (ul-indent)
docs/howto/support/raise-issues.md:47:5: MD007: Unordered list indentation [Expected: 2, Actual=4] (ul-indent)
docs/howto/support/raise-issues.md:50:5: MD007: Unordered list indentation [Expected: 2, Actual=4] (ul-indent)
docs/howto/support/raise-issues.md:51:5: MD007: Unordered list indentation [Expected: 2, Actual=4] (ul-indent)
docs/howto/support/raise-issues.md:63:5: MD007: Unordered list indentation [Expected: 2, Actual=4] (ul-indent)
docs/howto/support/raise-issues.md:72:5: MD007: Unordered list indentation [Expected: 2, Actual=4] (ul-indent)
docs/howto/support/raise-issues.md:76:5: MD007: Unordered list indentation [Expected: 2, Actual=4] (ul-indent)
docs/howto/support/raise-issues.md:77:5: MD007: Unordered list indentation [Expected: 2, Actual=4] (ul-indent)
docs/howto/support/raise-issues.md:104:6: MD007: Unordered list indentation [Expected: 4, Actual=6] (ul-indent)
docs/howto/support/raise-issues.md:122:6: MD007: Unordered list indentation [Expected: 4, Actual=6] (ul-indent)
docs/howto/support/raise-issues.md:123:6: MD007: Unordered list indentation [Expected: 4, Actual=6] (ul-indent)

[fghaas]

Well it's rather simple: if the linter is wrong, we'll just override the linter. :) I've pushed a fixup commit to that effect that you can subsequently squash into yours. I have a few minor notes on the substance of the PR too, I'll get to that in a bit.

[fghaas]

Thanks! This looks pretty good; sorry for the slow review. I have a few suggestions. Please see the inline comments.

[AboveHero]

Oops. I accidentally force pushed without comitting...

[fghaas]

Fixed the last minor outstanding changes, rebased on current main, and brought back the fix to the linter configuration that was accidentally dropped in the force-push. This looks good to me now; I'll go ahead and merge/publish. Thank you!