Edit: Add codelens shortcuts

[umpox]

Description

This PR:

• Adds keyboard shortcuts to common Edit codelens actions (Accept, Retry, Undo, Cancel)
  • These shortcuts are only enabled when an Edit is in an active actionable state, and it is in a visible document. This will help reduce the risk of these shortcuts becoming an annoyance if a user doesn't use Edit much.
• Updates "Retry" text to show "Edit & Retry"

Test plan

Single edit:

1. Create an edit
2. Try undo/retry/save shortcuts

Multiple edit (actions nearest edit):

1. Create multiple edits
2. Try undo/retry/save shortcuts and confirm that they only trigger against the nearest edit to the cursor position

Shortcut enablement:

1. Create an edit
2. Leave the file
3. Try undo/retry/save shortcuts. Confirm nothing happens
4. Return to the file
5. Try undo/retry/save shortcuts. Confirm they work

[abeatrix]

Left comments/questions inline. I'm wondering why the current e2e test is passing when the code lens title has changed 🤔 Do we also want a shortcut for ShowDiff?

[abeatrix]

Do you know why this is not affecting the e2e test where we only look for Edit?

[umpox]

Where we look for Retry? I think it's because the text is still there. I'll update the e2e test so it matches exactly

[toolmantim]

Looking great!

A few things:

• When an edit is running, the cancel shortcut (opt-z) doesn't seem to work
• Can we move Show Diff to the end?
• Can we hide the generic Cody Code Lenses if we have edit code lenses, so we don't get the double up seen in the below?
• I tested out a few different labelling formats (see below), I think fix typo #2 is the best (parentheses) — wdyt?

1:

Without the generic Cody lens:

2:

Without generic Cody lens:

3:

[umpox]

@toolmantim

When an edit is running, the cancel shortcut (opt-z) doesn't seem to work

Fixed

Can we move Show Diff to the end?

Done. Do you think we should include a shortcut for it too?

I tested out a few different labelling formats (see below), I think #2 is the best (parentheses) — wdyt?

Agree. Updated

[umpox]

Can we hide the generic Cody Code Lenses if we have edit code lenses, so we don't get the double up seen in the below?

@toolmantim I looked briefly into this. I think we can do this but it'll be a follow up PR and require some refactoring of the Cody codelens so we can easily hide this for a location within a particular document.

I think we should also consider what to do about this codelens first. It's disabled by default so we should either enable it fully or rethink how we show it so we can enable it by default

[toolmantim]

Looking good!

Done. Do you think we should include a shortcut for [Show Diff] too?

Maybe not, to keep keyboard shortcut footprint low? Or do you think it's weird not having one? Either way, can be a follow-up.