Fix version specific notes

[reithor]

Fix version specific notes for releases <=v2.1.1 and <=v2.4.1

[adriendupuis]

I would prefer

Suggested change

	### A. Update from <=v2.1.1
	### A. Update from earlier than v2.2

If not, maybe the use of ≤ instead of <=

Suggested change

	### A. Update from <=v2.1.1
	### A. Update from ≤v2.1.1

[reithor]

• I used "<=" because I have seen it here https://doc.ibexa.co/en/2.5/updating/from_1.x_2.x/update_app_to_2.5/#c-prepare-for-pulling-changes
• "earlier than" is less specific than "<=v2.1.1"

but I am definitely fine with "from earlier than v2.2" (or v2.2.0)

[DominikaK]

@reithor, in general, can you explain the reason for this change? We use the same structure for all update pages (see https://doc.ibexa.co/en/master/updating/from_3.3/update_from_3.3/#v332 for example), so changing it here would require reformulating the headings everywhere in the update section for consistency.
If I understand correctly and the issue is: "we are updating to v2.2, not from v2.2", I'd prefer rephrasing this introductory sentence:

Suggested change

	When updating a release **earlier than v2.5.0**, some version-specific changes are required.
	First, perform version-specific steps depending on which version you are updating to.

[reithor]

@DominikaK : changing the structure is not neccessary - I just thought it woul be clearer.
The whole point of the PR is that :
"A. v2.2" --> should be "A. Update from earlier than v2.2"
"B. v2.5" --> should be "B. Update from earlier than v2.5"

[reithor]

replaced by #1609