Consider setting .develop log level to default to reporting to Sentry

[steamclock-bot]

Automatically generated from steamclock/steamclog-swift#82

I'm not sure why we decided against this originally, but since we're able to determine which build a report comes from in Sentry this seems like it makes sense to me?

[ssawchenko]

Given Sentry limits it seems risky to default debug builds to send Sentry reports. Even after our TechWG discussion we did not change the LogLevel presets to allow for this. Right now there is no way for us to manually change only the remote logging level, but we could look at adding the ability to enable it.

Some ways we could support this:

1. Add a custom LogLevelPreset, where the caller indicates the exact levels they want:

class Custom(val consoleLogLevel: LogLevel, val diskLogLevel: LogLevel, val remoteLogLevel: LogLevel): LogLevelPreset()

2. Make the remote level mutable so that the calling application can modify only it

[ssawchenko]

I think we can leave this as an advanced feature for 2.1.

[ssawchenko]

Personally I see no reason why we cannot go ahead with adding the Custom preset option in 2.1. This seems like it would be useful in development environments when we need complete control over how we are logging.