Release notes should use master bug as the primary JBS bug id

[jerboaa]

In the OpenJDK projects the individual commits to any tree refer to a change by means of a bug, the so-called master bug. For example in the jdk25u tree it's this for JDK-8348760:

$ git log --grep 8348760
commit 6c48f4ed707bf0b15f9b6098de30db8aae6fa40f (tag: jdk-25-ga, tag: jdk-25+36)
Author: Prasanta Sadhukhan <psadhukhan@openjdk.org>
Date:   Tue Aug 12 17:15:36 2025 +0000

    8348760: RadioButton is not shown if JRadioButtonMenuItem is rendered with ImageIcon in WindowsLookAndFeel
    
    Reviewed-by: prr, aivanov
    Backport-of: e29346dbd6328dcadc347a70d8c06ce141efef02

Yet, in the release-notes JSON this info is being presented as:

  {
    "id": "JDK-8365202",
    "title": "RadioButton is not shown if JRadioButtonMenuItem is rendered with ImageIcon in WindowsLookAndFeel",
    "priority": "1",
    "component": "client-libs",
    "subcomponent": "client-libs/javax.swing",
    "link": "https://bugs.openjdk.java.net/browse/JDK-8365202",
    "type": "Backport",
    "backportOf": "JDK-8348760"
  }

Which results in the release notes on the website to show the bug as JDK-8365202 instead of JDK-8348760. For LTS releases most bugs would be of type Backport and for those bugs we should list the master bug number instead of the backport bug which usually doesn't even have a description. All the relevant info is in the master bug.

Please move this to the correct place. I can see this either being fixed in the JSON or in the website.