Update planner tool to set both partitioning param index and partitionin...

...g param value,

regardless of whether statement has been compiled to a parameterized plan.

Add the tests which caught this bug.
The declaration of msg and the assertTrue should be moved inside the catch block where it has a chance of passing.
It would make sense for the assertTrue in that case to take a value for its initial (too rarely used) String argument -- something like:

assertTrue("The message of the caught exception \"" + pce.toString() + "\" on statement \"" + stmt + "\" does not contain the expected pattern \"" + expectedMsg + "\"", msg.contains(expectedMsg));

If the catch block then contained an early return, the block could be followed by:
fail("Statement \"" + stmt + "\" failed to throw a ProcCallException -- expected one matching \"" + expectedMsg + "\"");

It's easier (higher leverage) to be more elaborate in the diagnostics in these utility functions -- we do not expect them to become hard-to-maintain boilerplate.