[11.x] Fix loadCount unwanted retrieved event

[imanghafoori1]

The #51276 issue mentions an extra model event fired when the loadCount is called. That is, in fact, relevant to all the load families of methods like loadMax, loadMin and etc that internally use loadAggregate.
The retrieved event is fired when the ->get() is called on line 92 and the event can be suppressed by wrapping it around the Model::withoutEvent.

• This is not backward compatible if an app relies on this flaw. (I do not know if the same solution has been suggested before)
• The added tests will fail without this change, due to the fired event.

[taylorotwell]

I'm not sure this is totally a bug? A model query is made therefore the event is fired?

[imanghafoori1]

@taylorotwell This is something totally unexpected as is the result of implementation details of load* methods.
I think Laravel may fire a special type of event dedicated to lazy eager loading instead, so it can be monitored while testing to ensure N+1 problem is avoided.

[sebapastore]

I have investigated the issue and arrived at the same conclusion as @imanghafoori1 regarding both the problem and its solution.

Additionally, I considered an alternative perspective: it is not necessary to make the query from the parent model; instead, it can be done directly from the related models.

Moreover, the documentation states: "Using the loadCount method, you may load a relationship count after the parent model has already been retrieved." While documentation may evolve, I believe this reflects the intended use of loadCount: the parent model should already be retrieved, thus it will not be retrived again during the loadCount call.