fix: throw SQLException for #getBoolean BIT(>1) - #2386

Throw SQLException instead of ClassCastException when calling
CallableStatement#getBoolean(int) on BIT(>1).

Currently when users call CallableStatement#getBoolean(int) on an out parameter of type BIT(>1) they get ClassCastException because the driver casts the result to a Boolean without checking the type first. This works for BIT(1) bit fails for BIT(>1) because then the type currently is PGobject. I know there are many related issues and PRs resolving around how we should treat bistring types

• Fixed issue #892 #1910
• PostgreSQL JDBC Throws PSQLException, Bit Types on getObject() #892
• Proper support for Bit String data type #908
• feat: Implement PgCallableStatement#getObject(int, Class) #698
• feat: Implement Statement#getObject(int, Class) without JSR-310 #813

This PR doesn't preclude any approach on these issues, it just changes the exception type for the current behavior.

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  There are many related ones but I didn't find any for this specific issue.

Changes to Existing Features:

• Does this break existing behaviour? If so please explain.
  Users get SQLException instead of ClassCastException. Users already need to catch SQLException so hopefully the impact isn't too big. Additionally the combination of CallableStatement and BIT(>1) may be quite low, otherwise we may have gotten bug reports.
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully run tests with your changes locally?