In "Messages Overview", show the bad_code first

It makes more sense to _first define the problem_, then solve it.

Mentions issue pylint-dev#7143

Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>

doc/exts/pylint_messages.py

@@ -272,8 +272,8 @@ def _generate_single_message_body(message: MessageData) -> str:
 
 *{message.definition.description}*
 
-{message.good_code}
 {message.bad_code}
+{message.good_code}
 {message.details}
 {message.related_links}
 """