feat: Add last runnables

[rockerBOO]

This allows users to run runnables that were run previously.
Example: Running previous test runnable and not needing to return
the cursor to the function position.

---

Would love feedback on this feature. Things like where should it be, how things are named, configuration options, and any other feedback. I put it into the hover menu because that's what I started to use, but there's also runnables.lua where this may work better or in addition to hover_actions.lua.

Thank you!

[simrat39]

Thanks for the PR, looks mostly good to me, but:

• I think we should always cache (not super expensive)
• And add a command to run the last runnable

Also, would it be possible to rework this to merge this into the modularize_and_inlay_rewrite branch as I'm planning to merge that into main very soon

[rockerBOO]

Ok, can do those.

I have been using this branch for a while, and it's mostly good, but it also catches undesired effects and causes them sometimes to fire off unexpectably.

For example,

• tests runnables work great
• go to definition seems to be a runnable that is captured
• but debug doesn't seem to run again (I have something else that correctly debugs the last one though)

So in the short term it might be good to not make it a general "last_runnable" but limit it to test runnables, specifically the ones for the test functions. My question is, should we expand the API to have specific types of runnables, and commands for those,

:RustLastTest
:RustLastDebug
:RustLastRunnable

or filter RustLastRunnable to not include go to definition type things and make debugger work with :RustLastRunnable.

:RustLastRunnable

Mostly want to pin down the API before a release that is consistent. Thank you, I will post a pull request to that branch.