Use textDocument/codeLens data in the actions menu when applicable #2

[SomeoneToIgnore]

Re-applies what's been reverted in #26832 with an action-related fix in 64b5d37

Before, actions were resolved only if data is present and either of the possible fields is empty:

zed/crates/project/src/lsp_store.rs

Lines 1632 to 1633 in e842b4e

	&& lsp_action.data.is_some()
	&& (lsp_action.command.is_none() || lsp_action.edit.is_none())

But Zed resolves completions and inlays once, unconditionally, and the reverted PR applied the same strategy to actions.
That did not work despite the spec not forbidding data-less actions to be resolved.

Soon, it starts to work due to rust-lang/rust-analyzer#19369 but it seems safer to restore the original filtering code.

Code lens have no issues with data-less resolves:
https://github.com/rust-lang/rust-analyzer/blob/220d913cbcd05f9b7635179a98c685f31821a572/crates/rust-analyzer/src/handlers/request.rs#L1618-L1620

so the same approach as completions and inlays is kept: resolve once.

Release Notes:

• N/A