text: Title: CHANGELOG.rst on master branch is flagged
  Body: ### AutoKey is a Xorg application and will not function in a Wayland session. Do you use Xorg (X11) or Wayland?
  
  Xorg
  
  ### Has this issue already been reported?
  
  - [x] I have searched through the existing issues.
  
  ### Is this a question rather than an issue?
  
  - [x] This is not a question.
  
  ### What type of issue is this?
  
  Documentation
  
  ### Choose one or more terms that describe this issue:
  
  - [ ] autokey triggers
  - [ ] autokey-gtk
  - [ ] autokey-qt
  - [ ] beta
  - [ ] bug
  - [ ] critical
  - [x] development
  - [ ] documentation
  - [ ] enhancement
  - [ ] installation/configuration
  - [ ] phrase expansion
  - [ ] scripting
  - [ ] technical debt
  - [ ] user interface
  
  ### Other terms that describe this issue if not provided above:
  
  _No response_
  
  ### Which Linux distribution did you use?
  
  _No response_
  
  ### Which AutoKey GUI did you use?
  
  None
  
  ### Which AutoKey version did you use?
  
  _No response_
  
  ### How did you install AutoKey?
  
  _No response_
  
  ### Can you briefly describe the issue?
  
  The 
  
  ![Image](https://github.com/user-attachments/assets/648e0de6-dd1d-4fa8-aec7-a63ce318f575)
  
   file on the **master** branch is flagged as failing. I see why it's flagged. It's got two section headers that are out of sequence (on [line 49](https://github.com/autokey/autokey/blob/87ace10981b00bee1e5069fb7b1b5da9770a80bb/CHANGELOG.rst#L49) and [line 223](https://github.com/autokey/autokey/blob/87ace10981b00bee1e5069fb7b1b5da9770a80bb/CHANGELOG.rst#L223). It's an easy fix.
  
  Note that the flag is for **Python 3.13**, which we don't yet use. It may have been put there by our PR tests because of a recent attempt to use **Python 3.13** that was since undone or it was put there by Sphinx or it was put there by GitHub as a friendly alert.
  
  The [CHANGELOG.rst](https://github.com/autokey/autokey/blob/develop/CHANGELOG.rst) file on the **develop** branch isn't flagged, but we do still make changes to the **master** branch that involve updating [CHANGELOG.RST](https://github.com/autokey/autokey/blob/master/CHANGELOG.rst) file on the **master** branch.
  
  Should I fix the issue? Don't bother?
  
  
  ### Can the issue be reproduced?
  
  Always
  
  ### What are the steps to reproduce the issue?
  
  1. Visit the [CHANGELOG.RST](https://github.com/autokey/autokey/blob/master/CHANGELOG.rst) page.
  2. Look above the document for the red x (marked with a green arrow in the image below).
  
  ![Image](https://github.com/user-attachments/assets/6244e4bd-4e21-4aab-a6f6-68bece2af915)
  
  
  ### What should have happened?
  
  No flag.
  
  
  ### What actually happened?
  
  _No response_
  
  ### Do you have screenshots?
  
  _No response_
  
  ### Can you provide the output of the AutoKey command?
  
  ```bash
  
  ```
  
  ### Anything else?
  
  _No response_
  <br/>
  <hr/>
  
  <details><summary>This repo is using Opire - what does it mean? 👇</summary><br/>💵 Everyone can add rewards for this issue commenting <code>/reward 100</code> (replace <code>100</code> with the amount).<br/>🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment <code>/try</code> to let everyone know!<br/>🙌 And when they open the PR, they can comment <code>/claim #1027</code> either in the PR description or in a PR's comment.<br/><br/>🪙 Also, everyone can tip any user commenting <code>/tip 20 @Elliria</code> (replace <code>20</code> with the amount, and <code>@Elliria</code> with the user to tip).<br/><br/>📖 If you want to learn more, check out our <a href="https://docs.opire.dev">documentation</a>.</details>