Rename IInitializeOptions to IPostConfigureOptions

[danroth27]

@divega @HaoK @ajcvickers

Both IConfigureOptions and IInitializeOptions have similar semantics but they are called at different times. Based on the names it sounds like IInitializeOptions would happen before IConfigureOptions, but apparently the order is the opposite. Can we come up with a better name that makes the behavior more obvious?

[HaoK]

Yeah don't disagree, need a name that conveys this is a PostConfigure phase.

[danroth27]

What were the scenarios that motivated adding this additional stage? The scenarios might help determine the name. I believe you said one of the scenarios was validation?

[HaoK]

Its basically Fixup/Validation, but we didn't want to bite off the entire validation feature for options, so we targeted only fixup/normalization, auth uses it to do things like establish defaults, in your azure options for example, I use this to set the authority

[HaoK]

So if we want an uber lame name that's extremely clear, service.PostConfigure<TOptions>() does fit the description.

[danroth27]

@glennc

[divega]

Is this about triggering all the IConfigureOptions to run?

[HaoK]

867583d