fix: enhance LSP client validation and menu actions

[Kakueeen]

• Updated the LSP client to include a validity check for the client before performing actions.
• Added a new method isValid() to the Client class to return the validity status.
• Modified the selectLspServer method to check if the client is valid before proceeding.
• Updated the context menu actions in LanguageClientHandler to enable or disable based on the client's validity.
• Introduced a new member variable isClientValid in ClientPrivate to track the client's state.

Log: This change improves the robustness of the LSP client interactions by ensuring actions are only available when the client is in a valid state.
Bug: https://pms.uniontech.com/bug-view-319109.html

Summary by Sourcery

Enhance LSP client robustness by tracking and exposing a validity state, conditionally initializing servers, and disabling related UI actions when the client is invalid

Enhancements:

• Track client validity in ClientPrivate with a new isClientValid flag
• Expose validity state via a new Client::isValid() method
• Mark the client as valid upon processing any server response result
• Skip redundant server selection and initialization in selectLspServer when client is already valid
• Only invoke initRequest in LSPClientManager if the client is invalid
• Disable language server–dependent context menu actions when the client is not valid

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deepin-mozart, Kakueeen

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• debian/deepin/OWNERS [deepin-mozart]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sourcery-ai]

Hey @Kakueeen - I've reviewed your changes - here's some feedback:

• Currently you set isClientValid on any JSON result—consider limiting it to initResult so the client isn’t marked valid prematurely.
• Add logic to reset isClientValid in error/shutdown handlers (e.g. calledError or exitResult) to avoid stale valid states after failures.
• The UI code repeats act->setEnabled(isClientValid) for each menu action—consider centralizing or looping over the relevant actions to reduce duplication.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}