Introduce PyAtomicRef and impl for PyObject.typ

[qingshi163]

@youknowone correctness and performance check?

[fanninpm]

Feel free to ignore those Clippy failures. @youknowone likely missed them in https://github.com/RustPython/RustPython/pull/3817.

[qingshi163]

#3970

[qingshi163]

Is this approach safe as we manaully require the reference to the pytype cannot across between the frames. Most of the case we use the pytype is either using pytyperef or using the reference immediately. @youknowone

[youknowone]

Oh, I missed your last push. I will check the changes soon.

[coolreader18]

(using PyAtomic instead of AtomicCell would fix the provenance errors in miri)

[qingshi163]

(using PyAtomic instead of AtomicCell would fix the provenance errors in miri)

let me try

[coolreader18]

Also, vm.frames should definitely be made private now, since it's now a safety thing that a frame cannot be popped off the frame stack + dropped before it's fully done running.

[qingshi163]

(using PyAtomic instead of AtomicCell would fix the provenance errors in miri)

let me try

Don't know why but seem like failing the compile when threading is off, any mistake about how to use PyAtomic? @coolreader18

[qingshi163]

(using PyAtomic instead of AtomicCell would fix the provenance errors in miri)

let me try

Don't know why but seem like failing the compile when threading is off, any mistake about how to use PyAtomic? @coolreader18

nevermind, it just the name conflict

[qingshi163]

@coolreader18 @youknowone review?