Normalize product files format

[marcwrobel]

Currently product files format is not consistent. There is no order and no formatting for attributes in the front matter, no fixed line length, no uniform markdown syntax (for example some page are using inline links, others are using links reference definitions - even when the link is not repeated).

This issue is about finding some basic and common rules in order to have a more consistent and readable format across all product markdown files.

[marcwrobel]

A few rules used in #2125 :

• Order of attributes (each block is separated by a blank line):
  1. Product level informations
  2. title / category / iconSlug / permalink / alternate_urls / versionCommand / releasePolicyLink
  3. changelogTemplate / releaseLabel / LTSLabel
  4. activeSupportColumn / releaseColumn / releaseDateColumn / eolColumn
  5. purls
  6. auto
  7. releases (each release is separated by a blank line)
• Max line length in description: 100 characters (exceptions are OK for instance for lines ending with a long link).
• No links reference definitions, except if link is repeated.
• No use of <abbr> (prefer the following syntax *[<acronym>]: <title>).
• Explain acronyms if it is not obvious or part of the product name (but try to avoid acronyms).
• changelogTemplate on one line, between double quotes if it is containing a liquid expression (that may prevent the link to be split on multiple lines by latest.py - to be confirmed).

And some existing rules:

• No quotes around dates.
• Versions and cycles always inside double quotes.

[captn3m0]

Created https://github.com/endoflife-date/endoflife.date/wiki/Style-Guide with rules from your comment above. Will expand over time.

[marcwrobel]

Now it's finished !