A module update during a rollout no longer blocks it

A new portal version checks every type before it starts serving. When a module update arrived while that check was running, the check could combine a type's previous definition with its updated files. The result failed to build, the check reported the type as broken, and the rollout waited until the new version was restarted.

The check now reads each type again immediately before building it. When the definition or its files changed since the check started, it builds the definition as it now stands, with the files that definition names, and when it cannot tell which files those are it reports the type as not checked instead of broken. A type that is genuinely broken still stops the rollout.