Resolve associative domain type expr module code in Dyno

[riftEmber]

Get associative domain type expressions resolving using their module code in Dyno, and re-enable testing for them.

This PR itself contains little work and mostly just drove Dyno work needed to support the module code.

Contributes to https://github.com/Cray/chapel-private/issues/6729.

Also includes:

• adding a dyno test for rectangular domain literals
• allowing helpResolveFunction to run on generic type constructors, per bug fix suggestion from Ben
• adjusting the handling of param == ? comparisons which was introduced in Dyno: Improve initialization of fields from non-matching types #26219, so that it gets specially handled rather than trying to resolve a defined == operator
• skipping recursing into TupleDecls in VarScopeVisitor to delay implementing call-init-deinit support for them for now
• an out-of-scope fix in CallInitDeinit::handleDeclarations where we clearly meant to reference type expr, but used init expr
• moving makeParam[Int,String,Bool] helpers in prims.cpp onto QualifiedType and use everywhere

Future work:

• resolve associative domain literals (Resolve associative domain literals #26534)
• implement call-init-deinit for tuple splitting declarations/assignments (https://github.com/Cray/chapel-private/issues/7021)

[reviewer info placeholder]

Testing:

• dyno tests
• paratest