Update ADOdb to 5.19
oci8 no longer needs special fetch mode with ADOdb 5.19

Fixes #15426
Use ADODB-specific constant instead of 'false'
Coding guidelines
Fix db_query_bound() to work with ADOdb::Execute()

In ADOdb v5.19 the Execute() method was modified to perform a strict
type check on the $inputarr parameter. Since that param defaults to
'false', database errors are triggered when the method receives 'null'
and there are no parameters to the query being executed.

Since db_query_bound() $p_arr_parms defaults to null, the problem occurs
almost everywhere. To fix this, we can either:

  1. set $p_arr_parms to array() when it is null
  2. defaut $p_arr_parms to array()

The 2nd option would cause errors with db_query_bound($sql, null)
calls, so we implement the first one as it offers better backwards
compatibility.

Function can be called like this (the first 3 methods being equivalent):
- db_query_bound($sql)
- db_query_bound($sql, null)
- db_query_bound($sql, array())
- db_query_bound($sql, array(1,2))
Call db_query_bound() with array() instead of null

This is not strictly necessary right now, but replacing known occurences
avoids future refactoring should we decide to change the default value
for $p_arr_parms to array() later on.
Update ADOdb to 5.19

- update the submodule
- back to ADODB_FETCH_ASSOC for oci8
- fix db_query_bound() $p_arr_parms null default issue

Fixes pull request https://github.com/mantisbt/mantisbt/pull/181
Fix E_RECOVERABLE_ERROR in event_api

Regression introduced by 5458f7020999317b35f403fa2a0e477d6182ec12.
NOTICE errors now display caller and line number