Hardening the "can you resolve this type" determination against bi-directional dependencies. Wolverine issue. Bumps to 13.0.1

Author: jeremydmiller

src/Lamar.Diagnostics/Lamar.Diagnostics.csproj

@@ -2,7 +2,7 @@
 
     <PropertyGroup>
         <Description>Adds diagnostic checks to the command line of your Lamar-enabled ASP.Net Core app</Description>
-        <Version>13.0.0</Version>
+        <Version>13.0.1</Version>
         <Authors>Jeremy D. Miller</Authors>
         <TargetFrameworks>net6.0;net7.0;net8.0</TargetFrameworks>
         <DebugType>portable</DebugType>

src/Lamar.Microsoft.DependencyInjection/Lamar.Microsoft.DependencyInjection.csproj

@@ -1,7 +1,7 @@
 <Project Sdk="Microsoft.NET.Sdk">
 	<PropertyGroup>
 		<Description>Lamar Adapter for HostBuilder Integration</Description>
-		<Version>13.0.0</Version>
+		<Version>13.0.1</Version>
 		<Authors>Jeremy D. Miller</Authors>
 		<TargetFrameworks>net6.0;net7.0;net8.0</TargetFrameworks>
 		<DebugType>portable</DebugType>

src/Lamar/Lamar.csproj

@@ -1,7 +1,7 @@
 <Project Sdk="Microsoft.NET.Sdk">
     <PropertyGroup>
         <Description>Fast ASP.Net Core compatible IoC Tool, Successor to StructureMap</Description>
-        <Version>13.0.0</Version>
+        <Version>13.0.1</Version>
         <Authors>Jeremy D. Miller</Authors>
         <TargetFrameworks>net6.0;net7.0;net8.0</TargetFrameworks>
         <DebugType>portable</DebugType>

src/Lamar/ServiceGraph.cs

@@ -513,7 +513,14 @@ internal void ClearPlanning()
 
     public bool CouldResolve(Type type)
     {
-        return FindDefault(type) != null;
+        try
+        {
+            return FindDefault(type) != null;
+        }
+        catch (Exception)
+        {
+            return false;
+        }
     }