support figwheel-connected sibling cljs repl

[bendlas]

Use Case

• Start figwheel via lein figwheel and have it configured to start an nrepl
• Connect to nrepl via C-c M-c
• Start a sibling cljs repl of figwheel-running type, to get into a figwheel-connected browser

Right now, this has to be done with a custom init form, which is annoying

---

Before submitting the PR make sure the following things have been done (and denote this
by checking the relevant checkboxes):

• The commits are consistent with our contribution guidelines
• You've added tests (if possible) to cover your change(s)
• All tests are passing (make test)
• All code passes the linter (make lint) which is based on elisp-lint and includes
  • byte-compilation, checkdoc, check-declare, packaging metadata, indentation, and trailing whitespace checks.
• You've updated the changelog (if adding/changing user-visible functionality)
• You've updated the user manual (if adding/changing user-visible functionality)

Thanks!

If you're just starting out to hack on CIDER you might find this section of its
manual extremely useful.

[bbatsov]

So, that’s the same as what we have right now, but with the difference it doesn’t start figwheel, right? Seems to me the naming is a bit confusing.

[bendlas]

Historically, the -sidecar moniker has been associated with starting figwheel in your process and dropping down to it via cljs-repl, for me.

I agree that there may be better names for it. What about figwheel-piggieback or figwheel-running?

[bbatsov]

Or maybe figwheel-connect? I’ll have to think about this a bit. @cichli Any thoughts?

[bendlas]

figwheel-connected implies the precondition of an active nrepl connection. I think I'll go with suggesting that.

[cichli]

Thanks for this! 🙌