dyno: relying on `isQueryRunning` in field genericity code seems incorrect about chapel

[mppf]

@DanilaFe - I don't think that we need computing "is a type generic" to work this way anymore at all. In particular, with recent changes related to asking for (?) for fields with generic declared type, we should be able to almost tell syntactically if a field is generic. (I say "almost" because for a generic-management class, I think we can identify that it is a generic-management class, but we don't have to resolve the class fields recursively). In particular, it's my expectation that we can now determine type genericity based upon the resolved field types without needing to delve into the fields of those types by relying on the syntactic markers (type and param are always generic as are fields with no type like var x; / const x; -- and var x: myGenericRecord(?) is generic but var x: myGenericRecord is an error to be discovered later in compilation).

See also https://github.com/Cray/chapel-private/issues/5603#issuecomment-1794965472