Fix Call#end_location w/ named arguments off-by-one error (#16542)

Author: Sija

spec/compiler/parser/parser_spec.cr

@@ -2653,6 +2653,13 @@ module Crystal
       assert_end_location "[1, 2,]"
       assert_end_location "foo(\n  &.block\n)", line_number: 3, column_number: 1
       assert_end_location "foo.bar(x) do; end"
+      assert_end_location "foo(bar: 123)"
+      assert_end_location "foo bar: 123"
+      assert_end_location "f foo(bar: 123)"
+      assert_end_location "f(foo bar: 123)"
+      assert_end_location "f foo bar: 123"
+      assert_end_location "f foo(x: 123, &.bar)"
+      assert_end_location "f foo x: 123, &.bar"
       assert_end_location "%w(one two)"
       assert_end_location "{%\nif foo\n  bar\n end\n%}", line_number: 5, column_number: 2
       assert_end_location "foo bar, out baz"

src/compiler/crystal/syntax/parser.cr

@@ -4851,7 +4851,12 @@ module Crystal
       end
 
       check :OP_RPAREN if allow_newline
-      end_location = token_end_location
+
+      # Prefer the end location of the last named argument when available.
+      # Using `token_end_location` would produce an off-by-one column
+      # in some cases (see issue #16092).
+      end_location = named_args.last?.try(&.end_location) unless allow_newline
+      end_location ||= token_end_location
 
       if allow_newline
         next_token_skip_space