dev/core#1360: Fix Programatic Installation Of Multiple Extensions on v5.19

[MiyaNoctem]

Overview

We have a drupal profile we use to install drupal sites with CiviCRM and some common extensions. When running the profile, CiviCRM is upgraded to v5.19. After that, the extensions are installed, however, the first extension installation causes a database exception to be thrown. It doesn't matter what extension is installed, every time, the installation of the first extension will fail.

Before

1. Upgrade upgrade_5_19_alpha1() creates a new field on civicrm_status_pref table. https://github.com/civicrm/civicrm-core/blob/master/CRM/Upgrade/Incremental/php/FiveNineteen.php#L69-L74
2. At the end of the installation of the first extension, schema is synched by comparing the columns of every table in CiviCRM with its correspondig logging table, however, the columnStats cache in \Civi:$statics has already been be initialized, with civicrm_status_pref table missing the new is_active column.
3. Schema is synched using cached values for columnStats. System erroneously detects log_civicrm_status_pref is missing the is_active column and tries to create it again, causing the exception to be thrown.

After

I've added a method that resets the columnStats cache when rebuilding the complete schema, in order to make sure we use the actual state of the schema when doing the sync.

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).

[MiyaNoctem]

@eileenmcnaughton , here's the PR sending the fix to v5.19 branch. Jenkins has finished building and testing.