Fix duplicate flows in dashboard tables caused by revisions

[ayuxsh009]

Description

This PR fixes an issue where dashboard tables using the
io.kestra.plugin.core.dashboard.data.Flows data source displayed duplicate entries for the same flow when multiple revisions existed.

Previously, the Flows data source returned all revisions of each flow, which caused one logical flow to appear multiple times in table charts. This change ensures that only the latest revision of each flow is returned, so each flow appears exactly once in dashboards.

---

🔗 Related Issue

Closes #14506

---

🎨 Frontend Checklist

This PR does not include any frontend changes.

---

🛠️ Backend Checklist

• Code compiles successfully and passes all checks
• All unit and integration tests pass

---

📝 Additional Notes

Root Cause
When using the Flows dashboard data source, the fetchData() and fetchValue() methods queried directly from the flows table, which stores one row per revision. This caused each flow to appear multiple times in dashboard tables.

Solution
Both methods were updated to query from fromLastRevision(true) instead of jdbcRepository.getTable(), applying the existing window-function-based filter that returns only the latest revision of each flow.

Testing

• All existing JDBC Flow Repository tests pass (58 passing)
• Manually verified that after editing the same flow multiple times, the dashboard table shows a single entry corresponding to the latest revision

---

Verification Screenshot*

After editing the same flow multiple times (creating multiple revisions), the
“All Flows” dashboard table now shows only one row for the flow (latest revision),
confirming that duplicate entries are no longer displayed.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.