Unify the execution of upgrade processes between Core and Modules

• Type: Story
• Status: Closed
• Priority: Major
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.3.0 CE GA1, Master
• Component/s: Database Upgrade Framework
• Labels:
  • 7.3-ce-ga1
  • fc_20_01
  • pt-upgrade-review
• Epic/Theme:
  • Upgrade-Improvements
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/83130

We are going to unify the behavior between Core and Modules regarding the upgrade framework. Ideally, in both cases minor and micro upgrade processes will run automatically having although customers will be able to control this with a property.

See:
https://github.com/achaparro/liferay-portal-ee/pull/59

Acceptance Criteria	Testing Scenarios	Test Strategy	Covered by backend test? (Yes/No)
	When a user wants to run minor and micro upgrade processes, these will run automatically using the property upgrade.database.auto.run	High	Yes (Marked as covered by backend tests, although this is covered by all the autoupgrade tests, including poshi tests