Data Cleanup does not remove obsolete shopping database tables after upgrade

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.3.X, Master
• Fix Version/s: 7.3.10.3 DXP SP3, 7.3.X, 7.4.1 CE GA2, 7.4.2 CE GA3, 7.4.13 DXP GA1, Master
• Component/s: Database Upgrade Framework
• Labels:
  • INACTIVE
  • liferay-dxp-73-sp3
  • liferay-fix-pack-dxp-3-7310
  • liferay-fixpack-dxp-3-7310
  • pt-upgrade-review
• Branch Version/s:
  7.3.x
• Backported to Branch:
  Committed
• Fix Priority: 3
• Sprint: Infra QA Sprint 53
• Git Pull Request: https://github.com/achaparro/liferay-portal/pull/907

Steps to reproduce:

• Start a 6.2 server with an empty database.
• Stop the server and see that shopping module tables have been populated. No entry corresponding to shopping module is present in Release_ table.
• Perform the upgrade to master/7.3.x.
• Start master/7.3.x server with the upgraded database.
• Go to Control Panel -> System Settings -> Upgrade -> Data Cleanup.
• Select 'Clean up shopping module data' and press 'Update'.

Expected result: According to Data Cleanup official doc, the process executes and removes all the data.

Current result: Shopping module related tables are still present in the database. Before removing the data, the process  looks for a "com.liferay.shopping.service" servletContextName in the release_ table, which does not exist.