Force memory for `absolute` var when target type differs #41031

Fixes #41031

When Y: T1 absolute X uses a different type than X (but same size), the target stayed regable. After inlining a function using such an alias (e.g. LB: TB absolute Result where TB has packed uint16 fields and Result is Pointer), field writes were compiled as LOC_SUBSETREG partial register updates without first loading the destination - all fields except the first ended up dropped.

Force memory for type-mismatched absolute targets.