Implement Field versioning to track modifications and trigger necessary updates

While solving an issue regarding the update of MeshedRegion.grid when MeshedRegion.set_coordinates is called, the need to associate a version number to fields seemed to make sense, because there is no way to intercept every potential data modification action which occurs on the data.
So for example, if someone were to modify the coordinates field's data directly without using the proper setter, that would not currently be detected. Same if an action were to modify it server-side. There would be no way to know the MeshedRegion.grid or any other object based on that data requires updating.

Start by tracing MeshedRegion.grid and MeshedRegion.set_coordinates, then inspect how the coordinates field can be modified directly or server-side. Clarify where field versions must be stored and observed, and define done as detecting every supported modification so dependent objects such as MeshedRegion.grid can be updated.

Written by the indexing model from the issue text.