Implement PartiQL bitwise operators

[am357]

Relevant Issue/Bug

• N/A

Requested Solution/Feature

• Add support for bitwise operators in PartiQL:

Operator	Description	Example	Result
||	concatenation	B'10001' || B'011'	10001011
&	bitwise AND	B'10001' & B'01101'	00001
|	bitwise OR	B'10001' | B'01101'	11101
#	bitwise XOR	B'10001' # B'01101'	11100
~	bitwise NOT	~ B'10001'	01110
<<	bitwise shift left	B'10001' << 3	01000
>>	bitwise shift right	B'10001' >> 2	00100

-- PostgresSQL: https://www.db-fiddle.com/f/g952RU7t652W32aiuWvsk6/8

SELECT B'110' | B'101' AS bit_or;
-- output: 111

SELECT 30 & 199 & 7 AS bit_and;
-- output: 6

Describe Alternatives

• We could use a custom function for this with the following sample signatures for the immediate narrow use-case:

INT -> INT -> INT // E.g., bit_and(2, 3)
INT -> INT -> INT -> INT // E.g., bit_and(2, 3, 4)

Additional Context

Prior Art:

1. PostgresSQL
   • https://www.postgresql.org/docs/9.4/functions-bitstring.html
   • https://www.db-fiddle.com/f/g952RU7t652W32aiuWvsk6/3
2. SQLite
   • https://www.db-fiddle.com/f/g952RU7t652W32aiuWvsk6/5
3. MySQL
   • https://www.db-fiddle.com/f/g952RU7t652W32aiuWvsk6/4
4. SQLServer
   • https://learn.microsoft.com/en-us/sql/t-sql/language-elements/bitwise-operators-transact-sql?view=sql-server-ver16

DoD (Definition of Done)

• The required types are implemented
• The operator precedence is determined and documented in partiql-doc or partiql-spec
• The implementation is merged to main
• The conformance tests are created
• Mini RFC?