Updated EOM and EOL hardcoded dates

[alongosz]

Question	Answer
JIRA issue	n/a
Target Ibexa version	v3.3
BC breaks	no

We've extended our 3.3 LTS EOM and EOL dates according to the Service Life. This PR aligns hardcoded dates used to display warning messages with that change.

I've also noticed that for OSS we check EOM date but display in a message "end of life" information. This seems to me as a copy-paste bug. Would be nice to get some confirmation on that part.

Checklist:

• Provided PR description.
• Tested the solution manually.
• Provided automated test coverage.
• Checked that target branch is set correctly (main for features, the oldest supported for bugs).
• Ran PHP CS Fixer for new PHP code (use $ composer fix-cs).
• Asked for a review.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[glye]

I can't confirm the copypasta bug suspicion, but it seems likely.