CHANGELOG: Only version in the headers

This is considered the best practice because this allows to have stable anchors (links) to each changelog version, making them predictable.

CHANGELOG.rst

@@ -16,47 +16,61 @@ UNRELEASED
 
 .. _`#70`: https://github.com/ESSS/pytest-replay/issues/70
 
-1.5.2 (2024-09-03)
+1.5.2
 ==================
 
+*2024-09-03*
+
 * Fix test outcome reported in the replay file (`#64`_).
 
 .. _`#64`: https://github.com/ESSS/pytest-replay/issues/64
 
-1.5.1 (2024-01-11)
-==================
+1.5.1
+=====
+
+*2024-01-11*
 
 * Dropped support for Python 3.6 and 3.7 (EOL).
 * Added official support for Python 3.10, 3.11 and 3.12.
 * Test execution order using ``--replay`` now follows the recorded order, not the collection order, as was always intended (`#52`_).
 
 .. _`#52`: https://github.com/ESSS/pytest-replay/pull/53
 
-1.4.0 (2021-06-09)
-==================
+1.4.0
+=====
+
+*2021-06-09*
 
 * Introduce new ``--replay-skip-cleanup`` option that skips the cleanup before running the command. This allows to keep previously generated replay files when running new commands.
 
-1.3.0 (2020-12-09)
-==================
+1.3.0
+=====
+
+*2020-12-09*
 
 * Replay files can now contain comments (``#`` or ``//``), to make it easy to comment out tests from them when trying to narrow the tests to find a culprit.
 
 
-1.2.1 (2020-08-24)
-==================
+1.2.1
+=====
+
+*2020-08-24*
 
 * Add proper support when running with ``xdist`` in a frozen executable.
 
-1.2.0 (2019-11-14)
-==================
+1.2.0
+=====
+
+*2019-11-14*
 
 * Change the format of the output to be able to add more information. The new output has new information such as
   start time, end time, outcome and the node identification, all these data is represented by each line being a ``json``
   format.
 
-1.1.0 (2019-11-11)
-==================
+1.1.0
+=====
+
+*2019-11-11*
 
 * Introduce new ``--replay-base-name`` option that lets users configure a different name of the replay file. Defaults to ``.pytest-replay``.