[lldb] Limit Py_buffer_RAII to SWIG < 4.1

The bug [1] this is working around was fixed in SWIG 4.1. The workaround
uses functions and constants that are not part of the limited API, which
I'm trying to eliminate to make LLDB compatible with the Python Limited
C API [2].

[1] swig/swig#1640
[2] #151617

Author: JDevlieghere

lldb/bindings/python/python-typemaps.h

@@ -3,6 +3,7 @@
 
 #include <Python.h>
 
+#if SWIG_VERSION < 0x040100
 // Defined here instead of a .swig file because SWIG 2 doesn't support
 // explicit deleted functions.
 struct Py_buffer_RAII {
@@ -15,5 +16,6 @@ struct Py_buffer_RAII {
       PyBuffer_Release(&buffer);
   }
 };
+#endif
 
 #endif // LLDB_BINDINGS_PYTHON_PYTHON_TYPEMAPS_H

lldb/bindings/python/python-typemaps.swig

@@ -637,9 +637,7 @@ template <> bool SetNumberFromPyObject<double>(double &number, PyObject *obj) {
 // These two pybuffer macros are copied out of swig/Lib/python/pybuffer.i,
 // and fixed so they will not crash if PyObject_GetBuffer fails.
 // https://github.com/swig/swig/issues/1640
-//
-// I've also moved the call to PyBuffer_Release to the end of the SWIG wrapper,
-// doing it right away is not legal according to the python buffer protocol.
+#if SWIG_VERSION < 0x040100
 
 %define %pybuffer_mutable_binary(TYPEMAP, SIZE)
 %typemap(in) (TYPEMAP, SIZE) (Py_buffer_RAII view) {
@@ -678,6 +676,8 @@ template <> bool SetNumberFromPyObject<double>(double &number, PyObject *obj) {
 %pybuffer_binary(const uint8_t *buf, size_t num_bytes);
 %pybuffer_mutable_binary(uint8_t *buf, size_t num_bytes);
 
+#endif
+
 %typemap(in) (const char **symbol_name, uint32_t num_names) {
   using namespace lldb_private;
   /* Check if is a list  */