Support connecting to Firebird via jdbcUrl containing the absolute path to fdb

[linghengqian]

For #29052.

Changes proposed in this pull request:

• Support connecting to Firebird via jdbcUrl containing the absolute path to fdb. The current PR was split from Add GraalVM Reachability Metadata and corresponding nativeTest for Firebird #34307 to facilitate review.
• This is due to Added firebird database type and parser module #33773 which does not support resolving jdbcUrls like jdbc:firebird://localhost:32783//var/lib/firebird/data/demo_ds_2.fdb.
• The current PR is affected by multiple external issues.
  • Done discussion around LICENSE for org.firebirdsql.jdbc:jaybird:5.0.6.java8 not being distributed under the ASF license at [FEATURE] Would consider replacing mybatis with hibernate? gravitino#4352 (comment) .
  • Due to the change of the minimum supported JDK version to JDK17 as reported by https://firebirdsql.org/en/news/jaybird-6-0-0-released , it is not possible to use org.firebirdsql.jdbc:jaybird:6.0.0 in unit tests of shardingsphere. We still need JDK8 to run unit tests.
  • According to some verification in /~https://github.com/FirebirdSQL/jaybird/blob/v6.0.0/src/test/org/firebirdsql/jdbc/FBDriverTest.java , it seems that the exception should not be thrown although a jdbcUrl like jdbc:firebirdsql:xxxxxxxx does not make sense.

---

Before committing this PR, I'm sure that I have checked the following options:

• My code follows the code of conduct of this project.
• I have self-reviewed the commit code.
• I have (or in comment I request) added corresponding labels for the pull request.
• I have passed maven check locally : ./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e.
• I have made corresponding changes to the documentation.
• I have added corresponding unit tests for my changes.
• I have updated the Release Notes of the current development version. For more details, see Update Release Note

[linghengqian]

• According to some verification in /~https://github.com/FirebirdSQL/jaybird/blob/v6.0.0/src/test/org/firebirdsql/jdbc/FBDriverTest.java , it seems that the exception should not be thrown although a jdbcUrl like jdbc:firebirdsql:xxxxxxxx does not make sense.
• What do you think? @TedCraft

[TedCraft]

According to the manual (/~https://github.com/FirebirdSQL/jaybird-manual/blob/master/src/docs/asciidoc/chapters/connection/connection.adoc#pure_java-type) the jdbcUrl format jdbc:firebirdsql:xxxxxxxxxxxx kinda makes sense, since it uses the legacy url format used in firebird. In this case, we just specify the database alias (or path) and the host and port are used by default (localhost:3050). But even though this url type is supported, according to the same manual, it is recommended to use the new url format.

[linghengqian]

• My understanding is that I should respect the behavior of the Firebird JDBC Driver's classes.

• There seems to be only the LGPL LICENSE for the Firebird JDBC Driver, so I would assume that everyone who uses both shardingsphere and the Firebird JDBC Driver would be affected by the LGPL. Maven's optional property is enough to comply with the ASF's requirements when distributing. I think there is no problem with PR at the moment.