ENH: add warning stacklevel when surfacing warnings from gdal.

[m-richards]

In _err.pyx

cython
    if err_class == CE_Warning:
        with gil:
            warnings.warn(clean_error_message(err_msg), RuntimeWarning)
        return

warnings surfaced by GDAL are bubbled up through the python warning system. Ideally this should probably get a stacklevel argument back to the read file call rather than showing a trace to pyogrio internals. I'm not sure why there isn't a stacklevel currently, perhaps this is a case where it's not easy to deduce what hte stack level should be as it depends on how it is reached.

[theroggy]

The primary reason there is no stacklevel parameter yet in some cython files is probably because there is no linter nagging about wanting one ;-).

But, it is indeed also a problem that most code paths in the cython code where warnings are emitted are not always called with the same "stack depth", so it is not possible at the moment to have the correct stack level in all situations.
I hope/think the skip_file_prefixes parameter available from python 12 will solve this: https://docs.python.org/3/library/warnings.html#warnings.warn