[9.x] Database queries containing JSON paths support array index braces, part 2

[derekmd]

Follow-up to #38391 meant to fix #26415
Related to today's PR #41756

1. DB::table('json_table')
       ->where('column->json_option[0]', 'foo')
       ->update(['column->json_option[0]', => 'bar']);

   The previous PR allowed the above query to match by JSON array index. But the fixes didn't apply to the Postgres database driver that overrides PostgresGrammer@wrapJsonSelector().

   Postgres does already support this:

   DB::table('json_table')
      ->where('column->json_option->0', 'foo')
      ->update(['column->json_option->0', => 'bar']);

   This fix allows the first PHP snippet to also work, bringing it in line with the other database drivers. SQL:

   -- before
   update "json_table"
   set "column" = jsonb_set("column"::jsonb, '{"json_option[0]"}', '"bar"'::jsonb)
   where ("column"->'json_option[0]')::jsonb = '"foo"'::jsonb;
   
   -- after, array index is extracted and braces are stripped
   update "json_table"
   set "column" = jsonb_set("column"::jsonb, '{"json_option",0}', '"bar"'::jsonb)
   where ("column"->'json_option'->0)::jsonb = '"foo"'::jsonb;

   Now the GitHub Actions config has a Postgres container I've added some integration tests.

2. Illuminate\Database\Schema\Grammars\Grammar@wrapJsonFieldAndPath() was a copy and paste duplicate from Illuminate\Database\Query\Grammars\Grammar and didn't receive the same fixes from the previous PR. It's a far edge case for column methods virtualAsJson() and storedAsJson() to use an array index but it probably makes sense for these classes to share a trait for compiling SQL containing JSON paths.

[derekmd]

    protected function wrapJsonPathAttributes($path, $quote = "'")
    {

I forget if Laravel considers protected method argument changes as breaking. I guess userland may extend PostgresGrammar and override this method.

[taylorotwell]

Thanks @derekmd! We would be pretty lost without you 😅