Handle differently the "memoized HTTP 404" cached responses

Currently, mvn local repo will "remember" that a repo reported 404 for artifact not present, and this fact is cached using ordinary update policy. To make mvn retry, -U is needed, that again, is too heavy handed, as it will force update always policy for everything...