Associate the mesh to the Nodes.coordinates field

[PProfizi]

This made the coordinates field unavailable for plotting and further handling by Post

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.81%. Comparing base (a9d68bb) to head (77618ba).
Report is 2 commits behind head on master.

❗ Current head 77618ba differs from pull request most recent head 2d9917e. Consider uploading reports for the commit 2d9917e to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1473   +/-   ##
=======================================
  Coverage   86.81%   86.81%           
=======================================
  Files          82       82           
  Lines        9631     9633    +2     
=======================================
+ Hits         8361     8363    +2     
  Misses       1270     1270           

[wiz-inc-572fc38784]

Wiz Scan Summary

IaC Misconfigurations
Vulnerabilities
Sensitive Data
Total
Secrets

[rafacanton]

Doesn't this create a sort of circular dependency? The mesh has a field inside (the coordinate field), that has the mesh as its support, that in turn has a coordinate field.... and so on

[PProfizi]

@rafacanton Notice that here I only do that when returning a "standalone" Field. Its associated mesh will indeed have a coordinates PropertyField, but that one will not have an associated mesh until we explicitly request it on its own

[rafacanton]

@PProfizi Yes, I understand that this association will not happen until this method is called. I cannot imagine of any potential downside that this can have down the stream (after having created the circ dep). @cbellot000 can you imagine of any? For example, what if you then add a new node to the mesh? This pushes back an id and 3 doubles in the coord field. Is there any problem in doing this with a field that has as a support the same mesh where this field is stored?

[PProfizi]

Hi @rafacanton , Hi @cbellot000 ,
If we cannot think of a way this may break something, we might as well merge it.
It is mandatory for several purposes when handling a PropertyField.