Add documentation for messages with assert in their name

[DanielNoord]

• Add yourself to CONTRIBUTORS.txt if you are a new contributor.
• Write a good description on what the PR does.

Type of Changes

	Type
✓	📜 Docs

Description

Code examples based on pylint-errors and my own work.

Ref. #5953.

These are a bit silly, but oh well... At least it shows how to avoid them.

[Pierre-Sassoulas]

The example are a bit silly here as it's hard to tell what te code should be. It should probably be "nothing" because the assert is useless ? What about # nothing, the assert was always true

[Pierre-Sassoulas]

Suggested change

	def test(param):
	if param:
	assertion_string = "There is an AssertionError"
	else:
	assertion_string = ""
	assert assertion_string
	from random import random
	def a_function_that_could_fail_the_assert():
	if random() > 0.5:
	return "something"
	return ""
	assert a_function_that_could_fail_the_assert()

I think the point is that asserting on a string litteral never fail.

[DanielNoord]

The example are a bit silly here as it's hard to tell what te code should be. It should probably be "nothing" because the assert is useless ? What about # nothing, the assert was always true

Yeah I'm going to change it to say something like that.