[TODO: Breaking] Change Raygun4Net dependency from Raygun4Net.NetCore to Raygun4Net.NetCore.Common

[ProRedCat]

We are currently inheriting the client from NetCore, which is just a wrapper for the base client in NetCore.Common

In the future, we plan to update this dependency, but this will be a breaking change

[velocitysystems]

@ProRedCat Just following up on this issue. What needs to be done here?

[ProRedCat]

@velocitysystems Right now Raygun4Maui inherits the Raygun4Net.NetCore, which is the broader NetCore provider. This constrains us to behaviour which the NetCore provider implements specific to NetCore.

In our other providers (Raygun4Net.AspNetCore, Raygun4Net.Extensions.Logging) we inherit from the Common library.

I believe there will be some breaking changes here, though I cannot quite remember what they were going to be. It's likely to do with the namespaces changing which would break some imports.

Another piece we likely were going to change here is to either remove the ILogger functionality that is tacked on to the provider, or replace it with the MS Logger - Raygun4Net.Extensions.Logging library we have.

The reason behind this is that the ILogger approach for logging is not the standard way to report errors in the base libraries. The recommended approach is to use the base library (e.g. Raygun4Maui) then use either something like the Raygun Serilog Sink, or the MS Logger one, to be able to use the ILogger to send errors to Raygun.

I'm unsure why the ILogger support was tacked on to this in the original version. In v2.0.0 we decided to keep it in for compatibility, but since we have richer support now through the MS Logger extension it would be better to switch to that.