[patch] updated manage release note for all patch version (#504)

Author: Abhishekkushawaha

src/mas/devops/data/catalogs/v9-260918-amd64.yaml

@@ -208,7 +208,8 @@ editorial:
   - title: '**Security updates and bug fixes**'
     details:
     - IBM Maximo Application Suite Core Platform [v9.2.6](https://www.ibm.com/support/pages/node/7288414), [v9.1.25](https://www.ibm.com/support/pages/node/7288415), [v9.0.31](https://www.ibm.com/support/pages/node/7288418)
-    - IBM Maximo Manage [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419)
+    - IBM Maximo Manage [v9.2.3](https://www.ibm.com/support/pages/node/7288426), [v9.1.24](https://www.ibm.com/support/pages/node/7288425), [v9.0.31](https://www.ibm.com/support/pages/node/7288424)
+    - Fix for Rotating Asset Inventory Balance Regression [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419)
     - FIPS [fips-140-2-mode-applicable-semeru-fips-140-2-restricted-security-profile-reaches-its-sunset-date-21-september-2026](https://www.ibm.com/support/pages/ibm-semeru-runtime-includes-restricted-security-profiles-used-maximo-application-suite-components-operating-fips-140-2-mode-applicable-semeru-fips-140-2-restricted-security-profile-reaches-its-sunset-date-21-september-2026?view=full)
   known_issues:
     - title: On or after 21 September 2026, on a FIPS-enabled cluster, the maxinst pod (<instance_id>-<workspace_id>-manage-maxinst) fails to start or crashes during the database initialisation/upgrade phase [Workaround](https://www.ibm.com/support/pages/node/7288522)

src/mas/devops/data/catalogs/v9-260918-ppc64le.yaml

@@ -75,7 +75,8 @@ editorial:
   - title: '**Security updates and bug fixes**'
     details:
     - IBM Maximo Application Suite Core Platform [v9.2.6](https://www.ibm.com/support/pages/node/7288414), [v9.1.25](https://www.ibm.com/support/pages/node/7288415), [v9.0.31](https://www.ibm.com/support/pages/node/7288418)
-    - IBM Maximo Manage [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419)
+    - IBM Maximo Manage [v9.2.3](https://www.ibm.com/support/pages/node/7288426), [v9.1.24](https://www.ibm.com/support/pages/node/7288425), [v9.0.31](https://www.ibm.com/support/pages/node/7288424)
+    - Fix for Rotating Asset Inventory Balance Regression [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419)
     - FIPS [fips-140-2-mode-applicable-semeru-fips-140-2-restricted-security-profile-reaches-its-sunset-date-21-september-2026](https://www.ibm.com/support/pages/ibm-semeru-runtime-includes-restricted-security-profiles-used-maximo-application-suite-components-operating-fips-140-2-mode-applicable-semeru-fips-140-2-restricted-security-profile-reaches-its-sunset-date-21-september-2026?view=full)
   known_issues:
     - title: On or after 21 September 2026, on a FIPS-enabled cluster, the maxinst pod (<instance_id>-<workspace_id>-manage-maxinst) fails to start or crashes during the database initialisation/upgrade phase [Workaround](https://www.ibm.com/support/pages/node/7288522)

src/mas/devops/data/catalogs/v9-260918-s390x.yaml

@@ -75,7 +75,8 @@ editorial:
   - title: '**Security updates and bug fixes**'
     details:
     - IBM Maximo Application Suite Core Platform [v9.2.6](https://www.ibm.com/support/pages/node/7288414), [v9.1.25](https://www.ibm.com/support/pages/node/7288415), [v9.0.31](https://www.ibm.com/support/pages/node/7288418)
-    - IBM Maximo Manage [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419)
+    - IBM Maximo Manage [v9.2.3](https://www.ibm.com/support/pages/node/7288426), [v9.1.24](https://www.ibm.com/support/pages/node/7288425), [v9.0.31](https://www.ibm.com/support/pages/node/7288424)
+    - Fix for Rotating Asset Inventory Balance Regression [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419)
     - FIPS [fips-140-2-mode-applicable-semeru-fips-140-2-restricted-security-profile-reaches-its-sunset-date-21-september-2026](https://www.ibm.com/support/pages/ibm-semeru-runtime-includes-restricted-security-profiles-used-maximo-application-suite-components-operating-fips-140-2-mode-applicable-semeru-fips-140-2-restricted-security-profile-reaches-its-sunset-date-21-september-2026?view=full)
   known_issues:
     - title: On or after 21 September 2026, on a FIPS-enabled cluster, the maxinst pod (<instance_id>-<workspace_id>-manage-maxinst) fails to start or crashes during the database initialisation/upgrade phase [Workaround](https://www.ibm.com/support/pages/node/7288522)