LPS-43264 Upgrade support
LPS-43264 Upgrade support - SF
LPS-43264 Apply to portal service.xml
LPS-43264 mvccVersion should go before everything else
LPS-43264 Regenerate
LPS-43264 Regenerate
LPS-43264 Reload LayoutSet object.
	This is because the previous LockLocalServiceUtil.lock() call which lanuched a new tx, caused previous tx's hibernate session to be flushed by LastSessionRecorderUtil.syncLastSessionState() which bumped up LayoutSet's ormVersion number in database.
	Similar issues may happen on lauching new tx when using LastSessionRecorderHibernateTransactionManager. Same solution can be applied to them.
LPS-43264 Transaction callback should carry on entity's identifier to reload rather than directly carrying the entity object.
	Transaction callback objects are created within current tx, but invoked after the current tx commit. If they directly keeping entity objects which are created/modified in current tx, on invoking the callback, the entity object's ormVersion in database must already changed, causing a stale update. The correct solution should be hold the entity's identifier and reload it on transaction call invocation.
LPS-43264 Reload Layout and LayoutSet.
	This is a typical example that showes we should avoid using ModelListener as much as possible.
	ModelListener is a flaw design which allows you to update entities quietly in the back end, this may invalid already loaded entities without any notification, on next usage of those overdued loaded entities, you may see an stale update.
LPS-43264 Reload for side affect changes
LPS-43264 SF