Enhancement, JDBC driver manager - configuration of the property validation

[speckyspooky]

For the enhancement of #1825 the JDBC driver manager got a change to validate the supported driver properties (PR #1831, BIRT 4.17).
Through this change the support of the DuckDB driver is possible.

The target of this change is to give BIRT a fallback configuration and a small individual configuration to handle which driver(s) should be validated an which driver(s) should be excluden from the validation.

The reason of it is that the change of the JDBC driver manager is a central change and change the standard behavior.
The second reason is that it could be that the JDBC driver information of the supported properties are not full defined
and with this additional change it can be handled.

The following options will be given as global system environment parameters of the JVM:

• birt.driver.property.validation.enabled
  o true, property validation is enabled (default)
  o false, property validation is disabled

• birt.driver.property.validation.excluded.drivers
  o unset, all drivers will be checked
  o is set, the listed drivers will be excluded from the validation
  o value, driver class name, for multiple driver listing a list splitted by comma separated class names can be used

** examples of global JVM parameters:**

• -Dbirt.driver.property.validation.enabled
  o the validation is disabled

• -Dbirt.driver.property.validation.excluded.drivers=com.microsoft.sqlserver.jdbc.SQLServerDriver
  o validation is enabled but without the driver of "SQLServerDriver"

• -Dbirt.driver.property.validation.excluded.drivers=org.duckdb.DuckDBDriver,com.microsoft.sqlserver.jdbc.SQLServerDriver
  o validation is enabled but without the both drivers of "DuckDb" & "SQLServerDriver"

[speckyspooky]

The PR #1833 is added for the change.

[speckyspooky]

The change is merged to the master branch.