Do not bail code action resolution when a quick fix is requested

[osiewicz]

Summary

When working on improving Ruff integration with Zed I noticed that it errors out when we try to resolve a code action of a QUICKFIX kind; apparently, per @dhruvmanila we shouldn't need to resolve it, as the edit is provided in the initial response for the code action. However, it's possible for the resolve call to fill out other fields (such as command).
AFAICT Helix also tries to resolve the code actions unconditionally (as in, when either edit or command is absent); so does VSC. They can still apply the quickfixes though, as they do not error out on a failed call to resolve code actions - Zed does. Following suit on Zed's side does not cut it though, as we still get a log request from Ruff for that failure (which is surfaced in the UI).
There are also other language servers (such as rust-analyzer) that fill out both command and edit fields as a part of code action resolution.

This PR makes the resolve calls for quickfix actions return the input value.

Test Plan

N/A

[charliermarsh]

Thanks! Assigning to @dhruvmanila.

[dhruvmanila]

I think this makes sense. We do this in ruff-lsp as well: https://github.com/astral-sh/ruff-lsp/blob/5488448c23274b9102747f867518b649f9234cfd/ruff_lsp/server.py#L1150-L1175