Array typehints for Update methods

[liamduckett]

Hey, this PR aims to improve static analysis around passing numerically keyed arrays to "update" methods. The following situations will now be reported by static analysers:

// 1. Model
$user = User::first();
$user->update(['foo', 'bar']);

// 2. Eloquent Builder
User::query()->update(['foo', 'bar']);

// 3. Query Builder
DB::table('users')->update(['foo', 'bar']);

These are already stubbed in Larastan, but this change will benefit those who do not use it.

• Eloquent Builder
• Query Builder
• Model

[shaedrich]

mixed might be improved:

Suggested change

	* @param array<string, mixed> $values
	* @param array<string, \Illuminate\Database\Query\Builder|\Illuminate\Support\Collection|\UnitEnum|mixed> $values

[liamduckett]

Hey, that feels like a more involved change than I was planning to make here (although I'm happy to implement it if desired by the maintainers).

I'm also not sure of the value of adding other types, in a union with mixed? With it being the top type, I believe X|mixed is equivalent to mixed (for any X).

[shaedrich]

Yeah, I would like to get rid of the mixed altogether but at a quick glance, I didn't know what were possible types for the default match case. I just thought: What good is it to retroactively add doc block types and then still end up with mixed? That might not be your fault, but I would be trying to avoid that to achieve an actually improved typing

[antonkomarev]

I think that mixed is enough here for now.

[taylorotwell]

I think it's fine for now.