improvement(startup): split into methods and add timing

[david-allison]

Note

Assisted-by: Claude Opus 4.6 - one commit:

setup("setupX") { setupX() } // move the setup() call inside setupX

Purpose / Description

I wanted a common method which would handle startup:

• So we could have one place where fatal and nonfatal initlilization errors occurred
• So we did not need to worry about methods throwing and hard-crashing on startup
• So we could profile startup times and be sure they're reasonable

Fixes

• Part of Improve startup process & notifying users of nonfatal component errors #20168

Approach

• introduce setup, which performs the logging & timing of methods
• Define dependencies using an object: AnkiContext or CrashReportingContext, and require their use via context providers

    context(_: AnkiContext)
    private fun initializeAnkiDroidDirectory() {}

    val anki = AnkiContext.apply { setupAnkiBackend() }
    with(anki) { initializeAnkiDroidDirectory() }

• Extract each setup operation into a method
• Combine and reorder methods where they make sense

How Has This Been Tested?

executed setupLogging in 11.416833ms
executed setupUsageAnalytics in 94.884708ms
executed performStartupLogging in 3.251458ms
executed setupContextMenus in 1.153625ms
executed makeBackendUsable in 143us
executed setupNotifications in 5.957541ms
executed setupAppLifecycleObserver in 579.041us
executed setupBackendChangeManager in 10.660333ms
executed setupWebView in 992.291us
executed setupBackend in 774.709us
executed initializeAnkiDroidDirectory in 1.840709ms
executed setupDayRollover in 1.921333ms
executed setupLifecycleLogging in 181.791us
executed setupTextToSpeech in 2.633416ms

Checklist

• You have a descriptive commit message with a short title (first line, max 50 chars).
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the Google Accessibility Scanner