Update compatibility docs of 7.1.0 and 7.2.0

[Miranlfk]

Purpose

This pull request updates the MySQL version compatibility information in the product documentation for multiple versions of the Identity Server. The main change is the addition of MySQL 8.4 and a generalization of the 8.0 version, ensuring that users are aware of support for the latest MySQL versions.

Documentation Updates:

• Updated the MySQL compatibility table in product-compatibility.md for versions 7.1.0, 7.2.0, and next to include MySQL 8.4 and generalize 8.0 support, replacing the previous specific mention of 8.0.4. [1] [2]

Summary by CodeRabbit

Documentation

• Updated MySQL database compatibility documentation across multiple product versions to reflect official support for MySQL 8.4 and 8.0 in addition to MySQL 5.7.

[coderabbitai]

Walkthrough

Updated MySQL DBMS compatibility documentation across three Identity Server versions (7.1.0, 7.2.0, and next). Changed the supported MySQL versions from "8.0.4, 5.7" to "8.4, 8.0, 5.7" in product compatibility tables.

Changes

Cohort / File(s)	Summary
MySQL Compatibility Documentation en/identity-server/7.1.0/docs/deploy/product-compatibility.md, en/identity-server/7.2.0/docs/deploy/product-compatibility.md, en/identity-server/next/docs/deploy/product-compatibility.md	Updated MySQL supported versions from "8.0.4, 5.7" to "8.4, 8.0, 5.7", adding explicit support for MySQL 8.4 and 8.0 while consolidating version references.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 MySQL versions dance and sing,

Eight point four joins the ring,

Eight and five-seven stand proud and tall,

Now compatibility covers them all! 🎉

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description covers purpose well but is missing required sections: Related PRs, Test environment, and Security checks from the repository template.	Add Related PRs, Test environment, and Security checks sections to match the repository's required description template.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Update compatibility docs of 7.1.0 and 7.2.0' is partially related to the changeset. It covers two of the three versions updated (7.1.0 and 7.2.0) but omits the 'next' version that was also modified, making it incomplete.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into master

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@en/identity-server/7.1.0/docs/deploy/product-compatibility.md`:
- Around line 65-67: Update the MySQL supported-versions cell in
product-compatibility.md by removing the incorrect "8.4" entry and ensuring the
cell lists the officially supported/tested versions (replace "8.4, 8.0, 5.7"
with "8.0.4, 5.7"); edit the <td> containing "MySQL" and its adjacent <td> that
currently contains the versions so it shows "8.0.4, 5.7".

In `@en/identity-server/next/docs/deploy/product-compatibility.md`:
- Around line 66-68: Update the MySQL supported versions cell in the
product-compatibility table by removing the incorrect "8.4" entry so it reads
"8.0, 5.7" instead of "8.4, 8.0, 5.7"; locate the table row containing the MySQL
<td> entry (the fragment with "<td>MySQL</td>" and the following versions cell)
and replace its contents accordingly, and add or update the citation to
reference the official WSO2 Identity Server compatibility page as the source.