yeah this is all post macOS 12.3, as Apple removed it, and hence the issue created/discussed here
I admit, I was being lazy, I didnt go check … and my machine had it installed in both /Library and /System/Library
iirc, apple will install things in /System/Library, and 3rd party (e.g. python.org) will install in /Library
(or sometimes ~/Library)
again, why Apple moved from a ‘framework’ to this simple /usr/bin/python3 is a bit unclear to me… and really the post is above the implications of this.
if we can’t figure it out, then probably I’ll got down the route of getting users to install from python.org. which we have previously done for the 64bit version.
its not ideal, as an extra install step, however, there are some benefits to this route, as it could be the same/similar for Mac and Windows (*)
(*) as we will also need to update the windows to python3 too, and I highly doubt windows has a python install ‘out of the box’ 
EDIT: Apple are currently supplying Python 3.8, having reviewed seeing some of the changes post 3.8… Ive decided we should go straight to the latest Python (3.10.5), and so will require users to install from python.org
this approach, means we will be less dependent on future Apple OS updates providing different versions of Python.