I imagine the 80% case will be only one options setup (probably config only), so the order won't actually matter most of the time.  

The other fairly common scenario will be adding a setup that runs either before or after config, which right now requires them to know Config runs at the -1000 order, which I agree is a bit hard to discover.  We could provide something in each framework which took a flag that could hide the OptionsOrder.Configuration +1/-1 bit.

```
services.AddIdentity().SetupOptions(overrideConfig: true, (options => options.PasswordLength = 10)