Enhancements: Allow users to register geospatial UDFs with various metastore options

For industry users utilizing HiveMetastore, IcebergRestCatalog, or other table metastore options, it may be helpful to provide an option for registering geospatial-related UDFs (user-defined functions) with the metastore of their choice. This would allow organizations to manage UDF registration more flexibly, instead of relying solely on built-in functions, which could complicate command resolution paths when many geospatial UDFs are present.

This is not an urgent request, but a tracking issue to consider adding support or documentation for registering Sedona geospatial UDFs with different metastore options (Hive, Iceberg, etc.), or offering guidelines for users with such needs.

Reference: [PR #2420 discussion](https://github.com/apache/sedona/pull/2420#discussion_r2452872125)

**Potential benefits:**
- Improved flexibility for enterprise deployments
- Avoid unnecessarily complicating function resolution for commands that do not use geospatial UDFs
- Support for advanced metastore setups

**Next steps:**
- Discuss implementation options
- Collect use cases from community/industry users
- Consider documentation or configuration options

Feel free to comment with additional ideas or requirements.

Start with the PR #2420 discussion referenced by the issue, then compare the HiveMetastore and IcebergRestCatalog use cases described here. Done requires an agreed implementation or documentation/configuration scope, along with collected requirements from affected users.

Written by the indexing model from the issue text.