fix: type checks for consistency when the same parameter is repeated (#4332, #4336)

[qykr]

Fixes #4332, #4336, adds a new invalid_reused_param_type e2e and fixes many existing ones.

[qykr]

Also fixed a typo:

-- internal/endtoend/testdata/params_placeholder_in_left_expr/postgresql/query.sql
SELECT * FROM users WHERE $1 = id;

-- name: FindByIDAndName :many
SELECT * FROM users WHERE $1 = id AND $1 = name;

I'm pretty sure having $1 repeated twice there is a typo, at least.

Also made the name auto inference engine a bit more powerful, from:

// internal/endtoend/testdata/select_subquery/postgresql/stdlib/go/query.sql.go
type SubqueryParams struct {
	Column1 sql.NullString
	Column2 sql.NullInt32
}

to:

// internal/endtoend/testdata/select_subquery/postgresql/stdlib/go/query.sql.go
type SubqueryParams struct {
	Alias sql.NullString
	A     int32
}

This was also one of the buggy e2e's described in #4336 by the way

[qykr]

Some may question whether or not using $1 multiple times should to be supported.

1. Some e2e tests already have this case (though not safely): params_duplicate, sqlc_arg, star_expansion_series
2. Many real life cases need repeated parameters
3. If you're in managed db mode, the database type checks for consistency already and this needs to be mirrored in the engine. In fact, my implementation is a bit more verbose. Pg error (internal/endtoend/testdata/invalid_reused_param_type/postgresql/stderr/base.txt):

# package querytest
query.sql:5:10: inconsistent types deduced for parameter $1

My error (internal/endtoend/testdata/invalid_reused_param_type/postgresql/stderr/managed-db.txt):

# package querytest
query.sql:5:10: parameter $1 has incompatible types: text, integer