- Updated Dagger modules with @Installin(SingletonComponent::class) annotation.
- AppComponent is converted to entry point aggregator. This is a temporary change. AppComponent will be removed when Hilt migration is done.
- Added @ApplicationContext to context parameters in modules.

Before this commit, app was crashing at start. Because some initializing stuff were working after Hilt injections. Now they are starting together with other injections.

Hilt test requires test application but test applications have some drawbacks. While real applications can inject before onCreate, test applications can only inject after onCreate. Thus, AppInitializer is created and will be used as a rule in test cases.

…bute

…alizer

- Added HiltAndroidTest to UserAgentTest
- Moved getUserAgent(), getDefaultUserAgent(), USER_AGENT_APPNAME from WordPress to AppInitializer

# Conflicts:
#	WordPress/src/main/java/org/wordpress/android/modules/AppComponent.java
#	build.gradle

Since SingletonComponent is recreated for each test cases, caching AndroidInjector and AppInitializer causes failing UI tests. AndroidInjector and AppInitializer are no longer cached for UI tests. But some static functions were crashing while AppInitializer is recreating. Added a boolean to AppInitializer to manage reinitializing of these functions.

Other classes are casting application to WordPress but WordPress couldn't be used in UI tests. And test application (WordPressTest) was crashing.
With this common abstract WordPress application, other classes can cast application to WordPress safely.