Enhance release notes

[adriendupuis]

Question	Answer
JIRA Ticket	N/A
Versions	5.0, 4.6
Edition	All

• Add "First release" pill for vX.0.0 and first release of an LTS Update (so "New feature" can continue to be used for a relevant feature addition to an existing package)
• Add compatible editions to LTS Update entries when missing
• Add version number when missing
• Filter right side bar ToC as well

Checklist

• Text renders correctly
• Text has been checked with vale
• Description metadata is up to date
• Redirects cover removed/moved pages
• Code samples are working
• PHP code samples have been fixed with PHP CS fixer
• Added link to this PR in relevant JIRA ticket or code PR

[github-actions]

Preview of modified files

Preview of modified Markdown:

• docs/release_notes/ibexa_dxp_v4.6.md
• docs/release_notes/ibexa_dxp_v5.0.md

[adriendupuis]

There are some possible improvements but not sure they worth it.

[mnocon]

Really like the idea, I'd just call it "initial release" instead of "first release"

[mnocon]

Suggested change

	[[= release_note_entry_begin("AI Actions " + version, '2024-12-13', ['Headless', 'Experience', 'Commerce', 'LTS Update', 'New feature']) =]]
	[[= release_note_entry_begin(
	"AI Actions " + version,
	'2024-12-13',
	['Headless', 'Experience', 'Commerce', 'LTS Update', 'New feature']
	) =]]

Extremely nitpicking, but what do you think about formatting it like this for future usages? No need to change the existing ones.

[adriendupuis]

Yes, when you have almost all pills on, it was hard to read.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud