Component field naming: name or longname? #258
Description
imod-python simulation/model/package objects use the DFN longname for field naming, rather than the terser name MF6/FloPy use. This is clearer and more accessible, if more verbose. The imod-python developers suggest doing the same in flopy 4.x, though this may increase the difficulty of migrating flopy 3.x scripts to 4.x, or perhaps finding a way to support either/both (longname via kwargs? duplicate package classes wrapping the normal ones? latter would be easy enough to generate)