NaverLoginInitializer
Captures the application Context at process start.
This is why NaverLogin.configure(NaverLoginConfig(...)) needs no Context parameter and can live in shared code. androidx.startup merges the provider into the consumer's manifest, so there is nothing for them to declare.
It captures the Context and nothing else. NAVER's own initialize opens a keystore-backed data store, so running it here would put that on the cold-start path of every app that ships this library, including the ones nobody ever signs in to; platformConfigure does it on first use instead.
Apps that strip androidx.startup.InitializationProvider (some do, to shave a few milliseconds off cold start) must call the Android-only NaverLogin.configure(context, config) instead. That is the only consequence.
Public because androidx.startup instantiates it reflectively from a manifest string — it is not part of this library's API, and consumer-rules.pro keeps it from being stripped.