feat: introduce ConverterProvider to control conversion behaviour

[vbarua]

ConverterProvider is a new class consumed by the various classes used to convert
between SQL <-> Calcite <-> Substrait

Its usage allows us to centralize the configuration of conversions behaviours,
which both helps to:

1. Provide clear standard defaults behaviours.
2. Provide a clear location to extend behaviours.

[vbarua]

I'm experimenting with overhauling the converter configuration to make changes like #647 easier to make, and to handle some of the concerns I had with #457 (review).

I still need to figure out how to structure the code to make it easy to utilize the DynamicConverterProvider, but I wanted to share the kernel of the idea.

[vbarua]

We wire in the same 4 converters (3 function converter + 1 type converter) in a number of places (SubstraitRelVisitor, SubstraitRelNodeConverter, ...). Instead of doing that, we can centralized the configuration of converters into one provider*. This would also allow us to provide extended providers, like the DynamicConverterProvider, that could implement the dynamic fallback behaviour in a single location rather that sprinkling it throughout the various parts of the codebase, which makes it very difficult to reason about.

* I'm not set on the name

[github-actions]

ACTION NEEDED

Substrait follows the Conventional Commits
specification for
release automation.

The PR title and description are used as the merge commit message. Please update your PR title and description to match the specification.