Fix COUNT(*) handling for Firebird

[makssent]

Changes proposed in this pull request:

• Fix COUNT(*) handling for Firebird
  • Fixed an issue where an incorrect data type was assigned to COUNT(*), which caused result packet corruption.
  • Added a Firebird-specific FirebirdProjectionIdentifierExtractor to support COUNT(*) queries without an alias.

---

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

[terrymanu]

• Good job adding the Firebird projection identifier extractor and tests—the implementation aligns with other dialects and is a step in the right direction.
  • Blocking gap: the new SPI is not loaded at runtime. proxy/dialect/firebird/pom.xml and jdbc-dialect/firebird/pom.xml don’t include the Firebird binder module, and distribution/bom/pom.xml doesn’t expose it. Without these dependencies, the new extractor won’t be on the classpath and COUNT labels will still fall back to the default. Please wire the module into the proxy/JDBC dialect POMs and BOM.
  • New logic for lowercasing function names and mapping COUNT to BIGINT lacks coverage. Please add a test (e.g., in FirebirdPrepareStatementCommandExecutorTest or a nearby test) that exercises describe handling/type resolution so regressions are caught.
  • Once these gaps are fixed, this should be safe to merge. Keep going—you’re close.

[makssent]

• Blocking gap: the new SPI is not loaded at runtime. proxy/dialect/firebird/pom.xml and jdbc-dialect/firebird/pom.xml don’t include the Firebird binder module, and distribution/bom/pom.xml doesn’t expose it. Without these dependencies, the new extractor won’t be on the classpath and COUNT labels will still fall back to the default. Please wire the module into the proxy/JDBC dialect POMs and BOM.

Yes, you’re right. I initially built the project with these dependencies, but later cleaned them up and forgot to rebuild the project and verify that everything was still working correctly. Thanks for your comments!