Does `CrashLoggingDataProvider` need to exist as a `protocol`?

[mokagio]

While working on #220, I was surprised to see CrashLoggingDataProvider as a protocol when the role it has in the code is that of a value type carrying configuration values.

If there's no external constraint on it being a protocol, I propose to convert it into a struct.

Having it as a struct would mean clients can create an instance directly, without the cruft of implementing a custom type conforming to it.

[jkmassel]

Just came across this and wanted to note that the reason it's a protocol is that some implementations might need dynamic values that change at runtime (for instance, userHasOptedOut). If we make that static, I assume it'd be instantiated on startup and the true value wouldn't be reflected until the app was fully closed and re-opened.