Use cached registry package info when local manifest is missing

Tuist now correctly reuses cached Swift Package Manager package info for registry dependencies even when the local Package.swift manifest is not present. Previously the cache freshness check required a manifest file and would fall back to reloading from the registry, which could slow or break dependency resolution. This change makes registry package loading faster and more reliable when the cached metadata is still up to date.