Discover nbb through nrepl describe #3466

[benjamin-asdf]

Fixes #3466

See issue.

The main idea for the dynamic discovery of the nrepl server capabilities was that you start out with a blank repl
and it augments itself by discovering the server.

The eval during startup was a hit of 1.6 seconds on my machine and 2 for vemv.

1. This check was currently only done for nbb connections (when connecting with cider-connect-clj)
2. For nbb, we do have a version from the describe op, so we already can say if it is nbb, or not

So the current change is to rely on the nrepl descibe op.

---

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 (eldev test)
• All code passes the linter (eldev 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)

[vemv]

Thanks much for responding so quickly!

A couple suggestions. Also, please also include a Changelog entry.

[vemv]

LGTM!

Please make sure to make the linter pass.

[vemv]

Thanks much!

I've cherry-picked this, preserving attribution.