fix(frontend): fix same version validation in change-mod-loader modal

[UNIkeEN]

Checklist

• Changes have been tested locally and work as expected.
• All tests in workflows pass successfully.
• Documentation has been updated if necessary.
• Code formatting and commit messages align with the project's conventions.
• Comments have been added for any complex logic or functionality if possible.

This PR is a ..

• 🆕 New feature
• 🐞 Bug fix
• 🛠 Refactoring
• ⚡️ Performance improvement
• 🌐 Internationalization
• 📄 Documentation improvement
• 🎨 Code style optimization
• ❓ Other (Please specify below)

Related Issues

fix #1286
maybe 修好了 #1285 的一部份（但引入了新的 bug）

Description

• Please insert your description here and provide info about the "what" this PR is solving.

Additional Context

• Add any other relevant information or screenshots here.

[Copilot]

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

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

[Copilot]

The useEffect dependency array is incomplete. The effect uses selectedOptiFine, selectedOptiFine.filename, and selectedModLoader.version, but only depends on selectedModLoader.loaderType.

This means when selectedModLoader.version or selectedOptiFine changes, the local state (selectedId and selectedType) won't be updated to reflect these changes. This could lead to UI inconsistencies where the displayed selection doesn't match the actual selected values.

Consider adding all used dependencies: [selectedModLoader.loaderType, selectedModLoader.version, selectedOptiFine]