Use new sedona_internal_err to avoid misleading datafusion internal err

[petern48]

I've found the use of Datafusion's internal_err! to be very misleading during development because it suggests the error is DataFusion's and not Sedona's (see the example texts). This PR adds a new macro to use instead.

Example (code was modified to intentionally trigger this internal error):

Before:

> select st_m(st_geomfromtext('point (1 1)'));
Internal error: unexpected dimension.
This issue was likely caused by a bug in DataFusion's code. Please help us to resolve this by filing a bug report in our issue tracker: https://github.com/apache/datafusion/issues

Now:

> select st_m(st_geomfromtext('point (1 1)'));
External error: SedonaDB internal error: unexpected dimension.
This issue was likely caused by a bug in SedonaDB's code. Please help us to resolve this by filing a bug report in our issue tracker: https://github.com/apache/sedona-db/issues

It would be nice to avoid the "External error:" prepending the message, but that seems to be the most reasonable of the available options without making an upstream change.

[paleolimbot]

I can't make the CI go on this repo because I don't have write access, but I think @jiayuasu can (and I think this problem will go away once your first PR merges).

[paleolimbot]

Thank you!

We'll need to get CI running to make sure, but this is great in principle!

[paleolimbot]

If we get the same linking errors in CI that we got before, you could try removing the back trace feature (we can always add it back in later if it turns out that we're having trouble debugging user errors)

[petern48]

Ah, that's what you meant

[petern48]

it passed !

[paleolimbot]

Thank you!