Add sync configure

[AaronPorts]

I think async configuration is not very suitable for browsers.

[dahlia]

You don't have to prepend await for calling configure() unless you'd like to use sinks which are AsyncDisposable (e.g., stream sink). I'll add docs about this.

[skeet70]

This isn't squaring with my experience. I added a configure call at the top of the entrypoint (without a top level await because it isn't available to me). My only sink is the console. Immediately after configure, environment loading code is called, and if the server exits due to a missing environment variable with a message, that message will not appear. I tried stalling for up to a second (which allowed other messages to be printed from other points in the application) before exiting, but it seems like the logger instance the environment variable code has access to is a dead reference or something.

A real sync configure would likely prevent these problems. Likely if I started this server 1000 times some number of them would output the message due to the event loop happening to finish initializing the logger before moving to the environment statements.

[dahlia]

It will be shipped with the next minor release, LogTape 0.9.0. See also the related docs in advance.

[dahlia]

Now it's shipped with LogTape 0.9.0!