Document backing store

Is your feature request related to a problem? Please describe.
When I first used this SDK, I modified objects that were returned but just for the needs of my script, with no intention of pushing back to the API the modifications. It didn't work properly and I had a couple of issues that I didn't understand at first, until I noticed that this SDK uses a notion of "backing store". I didn't dig deeper what it was but now I understand thanks to this description in the Java Graph SDK for the "backing store" and "dirty" mechanisms which I believe are the same as in this Python SDK.

Describe the solution you'd like
If it's indeed the same thing, please raise awareness about it in the README (or elsewhere) to reduce confusion

Describe alternatives you've considered
Perhaps I could have spent more time and managed to find the article myself, or this https://learn.microsoft.com/en-us/openapi/kiota/models#backing-store

Revisa el README y las descripciones vinculadas del backing store de Microsoft Graph Java y Kiota. Confirma cómo funcionan el backing store y los dirty mechanisms del Python SDK, y documéntalos en el README o en otro lugar apropiado para que los usuarios entiendan cuándo se registran los cambios en los objetos devueltos o cuándo se envían de vuelta a la API.