Code Gen: Use strict map rather than lazy map in loop analysis

We were ending up with a big 1GB thunk spike as the fmap operation did not force the key values promptly.

This fixes the high maximum memory consumption when compiling the mmark package. Compilation is still slow and allocates a lot more than previous releases.

Related to #19471 (closed)

Before:

After: