I found a bug and traced down relevant pieces of it, but haven't figured
out how to fix the behavior of org-capture where `:prepend t`

`:clock-resume` works with and clock data from `:clock-in t` is visible
with:

```
(setq org-capture-templates
'(("t" "Todo" entry (file+headline "file.org" "File")
  "* TODO %?"
  :clock-in t
  :clock-resume t)))
```

If you add prepend into the mix though:

```
(setq org-capture-templates
'(("t" "Todo" entry (file+headline "file.org" "File")
  "* TODO %?"
  :clock-in t
  :clock-resume t
  :prepend t)))
```

You can no longer see the clocking data. Not the worst thing... right?

Well, :clock-resume depends on the clock-data being before point-max of the
capture buffer.

Causing the part that resumes the previous clock to never fire in
org-capture-finalize:

```
(and org-capture-clock-was-started
    org-clock-marker
    (eq (marker-buffer org-clock-marker) (buffer-base-buffer))
    (>= org-clock-marker (point-min))
    (< org-clock-marker (point-max))) ;; clock marker when :prepend t is
past point-max
```

My versions are:

Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @
/home/cody/.emacs.d/straight/build/org/)
GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.10)