release-22.1: sql: hide number of placeholder

[blathers-crl]

Backport 1/1 commits from #88215 on behalf of @maryliag.

/cc @cockroachdb/release

---

Previously, placeholder values were kept as is
for fingerprint creation, meaning IN ($1, $2)
would be a different fingerprint than IN ($2, $1) even though they should be the same.
This commit replace all placeholder values with $1, so we
can still know it was a placeholder, but we don't care about the
number of the placeholder itself.
This is the simplest solution to solve this problem. Other
options (e.g. replace with $_ or p_) were considered but
ultimately they would require other modification on the parser code
to accept these values.

Previously:
SELECT * FROM t WHERE v IN ($1, $2) -> SELECT * FROM t WHERE v IN ($1, $2)
SELECT * FROM t WHERE v IN ($2, $1) -> SELECT * FROM t WHERE v IN ($2, $1)

Now:
SELECT * FROM t WHERE v IN ($1, $2) -> SELECT * FROM t WHERE v IN ($1, $1)
SELECT * FROM t WHERE v IN ($2, $1) -> SELECT * FROM t WHERE v IN ($1, $1)

Fixes #88074

Release note (sql change): The index of a placeholder
is now replaced to always be $1 to limit fingerprint creations.

---

Release justification: low risk, high benefit change

[blathers-crl]

Thanks for opening a backport.

Please check the backport criteria before merging:

• Patches should only be created for serious issues or test-only changes.
• Patches should not break backwards-compatibility.
• Patches should change as little code as possible.
• Patches should not change on-disk formats or node communication protocols.
• Patches should not add new functionality.
• Patches must not add, edit, or otherwise modify cluster versions; or add version gates.

If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.

• There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
• The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
• New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
• The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

• What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
• Will this work in a cluster of mixed patch versions? Did we test that?
• If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

[cockroach-teamcity]

This change is 

[xinhaoz]

Reviewed all commit messages.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @maryliag and @matthewtodd)