text: Title: Support Oracle 23ai BOOLEAN datatype
  Body: ### Describe the bug
  
  The latest Oracle DB release as of 7/22/24 - DB23AI - Supports native "BOOLEAN" types, whereas the type used to be captured by a SMALLINT. As a result, the documentation and behavior around CamelCase type "Boolean" is now out of date for Oracle DB:
  
  https://support.oracle.com/knowledge/Oracle%20Database%20Products/3002488_1.html
  """
  Unlike [String](https://docs.sqlalchemy.org/en/20/core/type_basics.html#sqlalchemy.types.String), which represents a string datatype that all databases have, not every backend has a real “boolean” datatype; some make use of integers or BIT values 0 and 1, some have boolean literal constants true and false while others dont. For this datatype, [Boolean](https://docs.sqlalchemy.org/en/20/core/type_basics.html#sqlalchemy.types.Boolean) may render BOOLEAN on a backend such as PostgreSQL, BIT on the MySQL backend and _SMALLINT on Oracle_
  """
  
  ### Optional link from https://docs.sqlalchemy.org which documents the behavior that is expected
  
  _No response_
  
  ### SQLAlchemy Version in Use
  
  2.0.31
  
  ### DBAPI (i.e. the database driver)
  
  cx_oracle
  
  ### Database Vendor and Major Version
  
  OracleDB 23
  
  ### Python Version
  
  3.10
  
  ### Operating system
  
  Linux
  
  ### To Reproduce
  
  ```python
  # create table w/ sqlalchemy
  op.create_table('test', sa.Column('col1', sa.Boolean())
  
  # query table in oracle
  select col1 from test;
  
  COL1
  ----
     0
  
  # create table using Boolean in oracle just fine
  create table test2 (col2 boolean);
  insert into test values (TRUE);
  
  Col2
  ----
  TRUE
  ```
  
  
  ### Error
  
  The result of the behavior mismatch is we get some nasty error when trying to run queries using the .is_ flag - the .is_(False) feature works just fine on Postgres, and then fails when using Oracle. The fix, for now, I believe is to use BOOLEAN instead of Boolean type.
  
  ### Additional context
  
  Oracle 23 only just came out recently, so I don't expect this to be done right away. See also: https://github.com/sqlalchemy/sqlalchemy/issues/10375