Tools: Ignore errors in design time DbContext discovery

[divega]

Any errors are thrown by creating the service container or trying to resolve DbContext from it in an ASP.NET Core apps should be ignored so that we can proceed to discover any IDesignTimeDbContextFactory<T>s.

From #9033 (comment), we believe we may have regressed.

cc @bricelam @ajcvickers

[lajones]

@divega What happens if you are trying to resolve a DbContext from an ASP.NET Core app? Could we put the errors out as debug/log messages to help debugging that scenario (but then continue on as you suggest above)?

[divega]

I think @bricelam’s PR puts the error in the log.

[bricelam]

Yep. Same logic as before: You'll see a warning containing the exception message, and --verbose will also give you the full stack trace and any inner exceptions.

[lajones]

@divega @bricelam Sounds great 👍