Cannot delete scraper

__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.

I don't know. I have a scraper - I can't delete it. It has no name, its organisation has been deleted. It is still running. I cannot get rid of it.

__Expected behavior:__
I expect it not to exist. I expect it to be deletable from the gui. I expect it to be deleted when the org it belongs to is deleted.

__Actual behavior:__

Every 10s:

influxd[3691954]: ts=2023-07-12T11:42:08.493538Z lvl=error msg="Unable to write gathered points" log_id=0izT7teG000 service=scraper scraper-name= error="database not found: c0d74c7f8afa5780"

__Environment info:__

* System info: Run `uname -srm` and copy the output here*

Linux 6.1.1-arch1-1 x86_64

* InfluxDB version: Run `influxd version` and copy the output here

InfluxDB 2.7.1 (git: 407fa62) build_date: 2023-07-12T11:43:36Z

* Other relevant environment details: Container runtime, disk info, etc

__Config:__
Copy any non-default config values here or attach the full config as a gist or file.

storage-series-id-set-cache-size = 100
http-bind-address = ":8086"

log-level = "warn"

__Logs:__
Include snippet of errors in log.

__Performance:__
Generate profiles with the following commands for bugs related to performance, locking, out of memory (OOM), etc.

```sh
# Commands should be run when the bug is actively happening.
# Note: This command will run for ~30 seconds.
curl -o profiles.tar.gz "http://localhost:8086/debug/pprof/all?cpu=30s"
iostat -xd 1 30 > iostat.txt
# Attach the `profiles.tar.gz` and `iostat.txt` output files.
```

The report names no source file, test, or entry point; start by reproducing the orphaned scraper behavior in the GUI and checking the repeated scraper log error. Done means an unnamed scraper whose organization was deleted can be removed and no longer runs or emits errors.

Written by the indexing model from the issue text.