Document FrameLocalsProxy behaviour quirks

Following PEP 667, https://docs.python.org/dev/reference/datamodel.html#frame-objects mentions that frame.f_locals may be a write-through proxy object, but doesn't really explain what that means.

Once https://github.com/python/peps/pull/3845 lands PEP 667 will contain such a description, but the main docs should at least cover the key behaviours:

• new instance on every attribute access
• two proxies with the same keys and values will still be unequal if they refer to different frames
• extra keys can be stored and are stored on the frame itself so they're shared across all proxies for the same frame
• keys corresponding to local variables can't be deleted
• .copy() (and any other API that produces a new container) returns a regular dict instance

Suggested location would be as a new 4th subsection under the frame objects section linked above. A "see also" from that new subsection back to PEP 667 would also be a useful addition.

Comienza con la sección sobre objetos frame de la documentación del modelo de datos de Python y revisa PEP 667, incluida la solicitud de cambios de PEP enlazada. Añade una cuarta subsección que describa los cinco comportamientos enumerados de FrameLocalsProxy y un enlace de consulta adicional de vuelta a PEP 667. Se considera terminado cuando la documentación principal explica la identidad del proxy, las claves adicionales compartidas, las variables locales que no se pueden eliminar y las API que producen diccionarios.