Local repository network connection failure should not fail silently

[anamnavi]

If a local repository is registered that is not available (for example private repository when machine is out of office), then an error is thrown. In the case where multiple repositories were requested to be checked, the error gets swallowed up and the user is not informed about the error. This PR ensures that the error is caught and populated in ErrorRecord and a warning is additionally written.

Note: With this fix an error and warning will both be written. A future fix will be made to ensure only 1 is written, but breaking up the fix so it can be taken in this release.

PR Summary

PR Context

Resolves #1923

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Documentation needed
    • Issue filed:
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and enumerated concerns in the summary.

[anamnavi]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[anamnavi]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).