GeezerVison

- Header files have moved around.
- Reference counting has changed. It appears to be python/cpython#130708 that's eliding some reference counting within functions and caused us to need to lower our expected reference count in a few places. NOTE: I'm not 100% sure this is the case; dis.dis is broken and won't show the function bodies so I can't confirm the new opcodes are being used.

- Header files have moved around.
- Reference counting has changed. It appears to be python/cpython#130708 that's eliding some reference counting within functions and caused us to need to lower our expected reference count in a few places. NOTE: I'm not 100% sure this is the case; dis.dis is broken and won't show the function bodies so I can't confirm the new opcodes are being used.

- Header files have moved around.
- Reference counting has changed. It appears to be python/cpython#130708 that's eliding some reference counting within functions and caused us to need to lower our expected reference count in a few places. NOTE: I'm not 100% sure this is the case; dis.dis is broken and won't show the function bodies so I can't confirm the new opcodes are being used.

- Header files have moved around.
- Reference counting has changed. It appears to be
  python/cpython#130708 that's eliding some
  reference counting within functions and caused us to need to lower
  our expected reference count in a few places. NOTE: I'm not 100%
  sure this is the case; but `dis.dis` shows the new opcode being used
  for the variables we're testing the refcount of.

Running that test on py3.14 fails:

    ____________________ test_strings_refcount _____________________

        def test_strings_refcount():
            # buffer with string data - not bytes nor unicode so that when builtin
            # string types are patched there is no case where bytes is created from the
            # same bytes, or unicode is created from the same unicode - only increasing
            # refcount of original object.
            data = bytearray([ord('a'), ord('b'), ord('c'), ord('4')])

            # first verify our logic on std type
            obj = bytes(data);      assert type(obj) is bytes
    >       gc.collect();   assert sys.getrefcount(obj) == 1+1   # +1 due to obj passed to getrefcount call
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    E       AssertionError: assert 1 == (1 + 1)
    E        +  where 1 = <built-in function getrefcount>(b'abc4')
    E        +    where <built-in function getrefcount> = sys.getrefcount

    golang/golang_str_test.py:301: AssertionError

That happens because on py3.14 the interpreter now does not add a
reference when passing on-stack argument to a function if it can prove
that is safe to do so.

Please see python/cpython#130708 and
python/cpython@f2379535 for details.

-> Adjust the test to account for that on py3.14 .

/reviewed-by @jerome
/reviewed-on https://lab.nexedi.com/nexedi/pygolang/-/merge_requests/39 + https://lab.nexedi.com/nexedi/slapos/-/merge_requests/1863#note_260064