LPS-43705 since the redirect is to another page in some situations, we need to use the crossLayout SessionMessages, because otherwise the ones of the portlet dockbar in page A won't be found in the same portlet in page B.
LPS-43705 autogenerated
LPS-43705 fetch won't throw an exception if it's not there, but will return null
Revert "LPS-43705 Support for Session Messages that work from different layouts (cross-layout). This is useful if you need to send a SessionMessage from a portlet in page A to a portlet in page B"

This reverts commit e29c24154d556941248156edb65055f04de3ba2b.
LPS-43705 Copy SessionMessages to MultiLayoutMessages (no changes)
LPS-43705 Rename constructor so it compiles
LPS-43705 Remove everything that does not have PortletRequest in the interface
LPS-43705 Delegate to SessionMessages
LPS-43705 add Julio's logic
LPS-43705 Remove imports
LPS-43705 Now that I think about it some more, it really is MultiSessionMessages (store it in the portlet request and request sessions). It just happens to be that we're using it for messages across multiple layouts.
LPS-43705 Update @author
LPS-43705 Apply
LPS-43708 Have StartupHelper to record startup status.
LPS-43708 Use StartupHelper rather than ThreadLocal
LPS-43989 Optimize ServiceBuilder arrayable parameter conjunction processing
LPS-43989 Regenerate
LPS-43989 SF
LPS-43958 Searching by a specific location that has United in the proper name will return all locations that have United in the proper name
LPS-43869 Fixed missing Selection Break field in Web Content Structure during portal upgrade.