TestJdbcChannelProvider throws OOME based on RNG values

TestJdbcChannelProvider uses a random number to test header overflow. This causes the JVM running the tests to sometimes die from an OOME. We should cap the test so overflows the header table value field size but stays within a reasonable limit. I've been able to verify this by increasing the maven test JVM heap size to values > 128MB (or more).