gh-127536: Add missing locks in listobject.c

[colesbury]

We were missing locks around some list operations in the free threading build.

• Issue: Free threading locking issues in listobject.c #127536

[corona10]

lgtm

[mpage]

Not for this PR, but do you think it would be worthwhile to audit the functions that we expect to be called with the per-object lock held and add _Py_CRITICAL_SECTION_ASSERT_OBJECT_LOCKED() or the equivalent where they're missing?

[colesbury]

Yes, I think additional _Py_CRITICAL_SECTION_ASSERT_OBJECT_LOCKED checks would make sense.

[miss-islington-app]

Thanks @colesbury for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13.
🐍🍒⛏🤖 I'm not a witch! I'm not a witch!

[miss-islington-app]

Sorry, @colesbury, I could not cleanly backport this to 3.13 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker e51da64ac3bc6cd45339864db32d05115af39ead 3.13

[bedevere-app]

GH-127613 is a backport of this pull request to the 3.13 branch.

[bedevere-bot]

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot s390x RHEL9 Refleaks 3.13 has failed when building commit 4060ef3.

What do you need to do:

1. Don't panic.
2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1575/builds/303) and take a look at the build logs.
4. Check if the failure is related to this commit (4060ef3) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1575/builds/303

Failed tests:

• test_site
• test_audit

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.refleak/build/Lib/test/audit-tests.py", line 587, in <module>globals()[test](*sys.argv[2:])
~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.refleak/build/Lib/test/audit-tests.py", line 541, in test_time
time.sleep(0)
~~~~~~~~~~^^^
File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.refleak/build/Lib/test/audit-tests.py", line 538, in hookraiseAssertionError('hook failed')
AssertionError: hook failed
k

[bedevere-bot]

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot s390x RHEL8 Refleaks 3.13 has failed when building commit 4060ef3.

What do you need to do:

1. Don't panic.
2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1440/builds/384) and take a look at the build logs.
4. Check if the failure is related to this commit (4060ef3) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1440/builds/384

Failed tests:

• test_site
• test_audit

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.refleak/build/Lib/test/audit-tests.py", line 587, in <module>globals()[test](*sys.argv[2:])
~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.refleak/build/Lib/test/audit-tests.py", line 541, in test_time
time.sleep(0)
~~~~~~~~~~^^^
File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.refleak/build/Lib/test/audit-tests.py", line 538, in hookraiseAssertionError('hook failed')
AssertionError: hook failed
k