Add kind and preferred flag for all Wingman code actions

[isovector]

#1458 suggests that Wingman export its code actions with descriptive LSP kinds so that editors can more easily filter them. This PR does that, under the refactor.wingman. prefix.

@TOTBWF @michaelpj please review. Does this do what you want?

[isovector]

This seems to be a success; I've managed to bind the code actions in my editor. What a great improvement!

[michaelpj]

Nice! My only quibble is with refactor.inline. These don't seem like they're mostly inlinings? refactor.rewrite might fit better, or maybe we should make up something like refactor.synthesis 😆

[isovector]

Fair enough. I was thinking about case split when I named them, which does sorta inline the definition. But I'd prefer to have a common prefix for all of the actions, so maybe just refactor.wingman. is the play here.

[michaelpj]

refactor.wingman seems totally reasonable. I don't think we need to invent some semantic grouping of these commands that doesn't exist. The reality is: it's all the wingman commands, and that's fine.

[Ailrun]

I'm not familiar to action kind things, but since tactics plugin resolves (or changes) some errors, it may be better to use quickfix.wingman.. WDYT?

CC: @michaelpj

[isovector]

Too slow, sorry! Feel free to file a bug if this is terribly worrisome!

[michaelpj]

They don't seem very quickfix-y to me, and I think a bunch of them work with holes, so they won't actually be fixing errors.

[Ailrun]

@michaelpj I mean a hole produces a compile error, so... But I'm not strongly inclined to anything :)