Useless upgrade processes run during the initial database creation

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.1.X, 7.2.X, 7.3.X, Master
• Fix Version/s: 7.4.13 DXP GA1, 7.4.3.4 CE GA4, 7.4.3.40 CE GA40, 7.4.3.41 CE GA41, 7.4.3.42 CE GA42, Master
• Component/s: Database Upgrade Framework
• Labels:
  • 7.2-should
  • 7.3-known-issues
  • 7.3-should
  • 7.4-known-issues
  • Pimientos_padron
  • fc_21_08
  • liferay-ga1-ce-740
  • liferay-ga2-ce-741
  • liferay-ga4-ce-733
  • liferay-ga5-ce-734
  • liferay-ga6-ce-735
  • liferay-ga7-ce-736
  • liferay-ga8-ce-737
  • pt-upgrade-review
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/105824
• Bug Type: Database Upgrade

Steps to reproduce it:

1. Startup master with a fresh database

Results:
Some upgrade processes run, for example:

2018-10-29 09:26:18.469 INFO  [main][UpgradeProcess:107] Completed upgrade process com.liferay.microblogs.web.internal.upgrade.v1_0_0.UpgradePortletId in 13 ms
INFO - Completed upgrade process com.liferay.microblogs.web.internal.upgrade.v1_0_0.UpgradePortletId in 13 ms
2018-10-29 09:26:18.799 INFO  [main][UpgradeProcess:93] Upgrading com.liferay.push.notifications.web.internal.upgrade.v1_0_0.UpgradePortletId
INFO - Upgrading com.liferay.push.notifications.web.internal.upgrade.v1_0_0.UpgradePortletId

And others that don't print traces such the one related to _configurationUpgradeStepFactory in RSSWebUpgrade are executed when it's not needed.

Expected results:
Those upgrade process are not executed.

Technical notes:
For web modules, we need to specify the upgrade path for clean installations, that upgrade path has to run from 0.0.0 to the latest defined schema version, however we usually forget to update it. Just check the previous examples.

To solve it we should either:

1. Review all web upgrade processes and create a SF rule to avoid future mistakes or
2. Create a framework to avoid to have to update that upgrade path anytime (preferred)