this prevents generating promises we don't use, which would get logged
by the node vm and spam the logs

I have no clue why I wrote that code 😭

It's trivial to have more than 128 requests in flight: open a busy
timeline, scroll a bit down, wait for many notes to arrive, scroll to
the top. The frontend will send "subscribe to note" messages for each
new note that it accumulated, all at once. We don't want to shut down
the connection in those common cases!

* the frontend opens 2 websockets at startup (I'm not completely clear
  why), and that `minInterval:1sec` was breaking the second connection
* as the comment says, "catching up" generates many noteSubscribe
  messages

we're doing the same thing that Fastify does in the non-streaming
ServerService

we were inconsistent with the colons, thanks to usedbunny for
noticing!

Co-authored-by: かっこかり <67428053+kakkokari-gtyih@users.noreply.github.com>

that is, silencing `foo.com` also silences `sub.foo.com`

as @fEmber noticed, if `findOneByOrFail` throws, we would have marked
the report as resolved, without logging that

this way, the whole operation fails (the frontend should not send us
ids of users that can't be resolved!)

the `inline` bit is not pretty, but does the job

Some remote instances may send garbage. If the `sensitive` value
passed to `driveService.uploadFromUrl` is not a boolean, eventually
we'll get an exception from the database complaining about that. This
change avoids that problem.

it's the same code that 5f7fc54e added
to `delete` and `deleteBulk`, with the extra check that we're not
deleting the same file we're setting