[Databricks] Allow registering Sedona functions with a custom prefix

Hi,

I’m trying to use **Apache Sedona** in Databricks, alongside the new built-in Databricks spatial SQL functions.

Right now, Sedona registers sql **ST** functions like st_distance, st_point ...
This causes name collisions with some Databricks’ native spatial functions.

It would be very useful if Sedona supported registering all SQL functions with a custom prefix, for example:

st_distance -> sedona_st_distance
st_point -> sedona_st_point

This way, Sedona functions can coexist with Databricks functions in the same notebook without conflicts.

Is this currently possible, or could it be added as a feature in a future release?

Thank you!

Start by tracing Sedona’s SQL function registration path for Databricks, focusing on where ST names are assigned. Verify the design with a notebook containing Databricks spatial functions; done means all Sedona functions can be registered under a caller-chosen prefix without collisions.

Written by the indexing model from the issue text.