Fix evaluate updating UI, when there is no editor active

[PEZ]

What has changed?

When we evaluate connect sequence afterCLJReplJackInCode provided code, we use evaluate.evaluateCodeUpdatingUI function. I don't know exactly why, but maybe it is because with UI we mean both the REPL window and the decorations in the active editor. But if there is no active editor, we run into trouble. Most commands and shortcuts for evaluating things in the active editor have when clauses that guards, but the jack-in should work regardless of active editor or not.

This code is very messy and in bad need of restructuring. With this PR I pile on to the technical debt, because I don't have a good idea about how the code should be structure. It's a tiny change, just checking that we have an editor before we go access it. All use cases that have this will continue to work as before, and use cases that don't, might start working, and if they don't, they didn't work before either.

In any case the issue exposing this problem is fixed by this.

• Fixes afterCLJReplJackInCode fails if no editor buffer open #2025

My Calva PR Checklist

I have:

• Read How to Contribute.
• Directed this pull request at the dev branch. (Or have specific reasons to target some other branch.)
• Made sure I have changed the PR base branch, so that it is not published. (Sorry for the nagging.)
• Updated the [Unreleased] entry in CHANGELOG.md, linking the issue(s) that the PR is addressing.
• Figured if anything about the fix warrants tests on Mac/Linux/Windows/Remote/Whatever, and either tested it there if so, or mentioned it in the PR.
• [ ] Added to or updated docs in this branch, if appropriate
• Tests
  • Tested the particular change
  • Figured if the change might have some side effects and tested those as well.
  • Smoke tested the extension as such.
  • Tested the VSIX built from the PR (so, after you've submitted the PR). You'll find the artifacts by clicking Show all checks in the CI section of the PR page, and then Details on the ci/circleci: build test.
• Referenced the issue I am fixing/addressing in a commit message for the pull request.
  • If I am fixing the issue, I have used GitHub's fixes/closes syntax
• Formatted all JavaScript and TypeScript code that was changed. (use the prettier extension or run npm run prettier-format)
• Confirmed that there are no linter warnings or errors (use the eslint extension, run npm run eslint before creating your PR, or run npm run eslint-watch to eslint as you go).

Ping @PEZ, @bpringe, @corasaurus-hex, @Cyrik