Renamed macro products are accepted from the cache

Macro cache artifacts whose product name differs from the target name (for example a DependenciesMacrosPlugin target whose executable artifact is named DependenciesMacros.macro) are now resolved correctly through the local, remote, and module cache paths. If a downloaded archive does not contain a matching artifact at all, the cache miss path is now taken gracefully rather than force-unwrapping a missing value.