Allow platform to handle main screen config change
Allow platform to handle main screen config change

The OverhaulActivity became the new MainActivity. OverhaulActivity
doesn't hold a WebView and so doesn't seem to require manual View
configuration management. The default is considered best practice for
most apps[0]:

  Note: Using this attribute should be avoided and used only as a last
  resort. Please read Handling Runtime Changes for more information
  about how to properly handle a restart due to a configuration change.

Our use of retained Fragment instances and shorter View hierarchies
keeps configurations changes, such as those on device rotation, speedy.
The default seems adequate.

Note: if this patch is not merged, we will need to handle configuration
changes manually in Views expect standard View lifecycles.

[0] https://developer.android.com/guide/topics/manifest/activity-element.html#config

Change-Id: I190bae2232d35a89a3e0d36f71322353141b2c80

SAGROUP2/apps-android-wikipedia,dbrant/apps-android-wikipedia,dbrant/apps-android-wikipedia,dbrant/apps-android-wikipedia,dbrant/apps-android-wikipedia,wikimedia/apps-android-wikipedia,wikimedia/apps-android-wikipedia,wikimedia/apps-android-wikipedia,SAGROUP2/apps-android-wikipedia,anirudh24seven/apps-android-wikipedia,anirudh24seven/apps-android-wikipedia,anirudh24seven/apps-android-wikipedia,anirudh24seven/apps-android-wikipedia,anirudh24seven/apps-android-wikipedia,SAGROUP2/apps-android-wikipedia,dbrant/apps-android-wikipedia,wikimedia/apps-android-wikipedia,SAGROUP2/apps-android-wikipedia,SAGROUP2/apps-android-wikipedia