[5.x] Query for entry origin within the same collection

[jasonvarga]

Seems to fix #10025

I'm honestly a bit skeptical about this fixing the issue, however in my tests, it definitely made a difference.

What I was doing was this...

In Tinkerwell, run this:

use Illuminate\Support\Facades\Http;
use Illuminate\Support\Collection;
use Illuminate\Http\Client\Pool;

$responses = collect(
  Http::pool(
    fn(Pool $pool) => Collection::times(
      50,
      fn() => $pool->get("http://the-site.test")
    )
  )
);

$responses->map
  ->status()
  ->countBy()
  ->all();

This will fire off 50 requests to the home page and output the number of each response status code.

While that's going, I would run artisan cache:clear from the site.

Before the PR, I would fairly consistently see the routeData on null error multiple times.

[
    200 => 43,
    500 => 7
]

After, I wouldn't see it. (I would occasionally see some other sorts of sporadic failures, but they were unrelated.)

[
    200 => 50,
]

The reason this seemingly unrelated line has anything to do with the error is because at some point along the way during building an index it needs to grab the origin. When you do Entry::find() (which is really just Entry::query()->where('id', $id)->first()) it'll need to load up all the id indexes for all collections. If you provide a collection to an entry query, it'll only load the id indexes for the collection(s) you pass it. In this case it'll load an index that's already loaded.

[afonic]

This seems to solve it for us!