LPS-49070 Revert LPS-46821, this makes it so that multiple related asset portlets cannot be used on the same page
LPS-49070 Revert LPS-47920 as it's no longer needed
LPS-49070 keep different struts-path, they are still useful
LPS-49070 Create a portlet filter for related assets portlets (no logic change)
LPS-49070 Clear render parameters before rendering the related assets portlet when no asset entry is selected, this is similar to what we were doing before
LPS-49070 Source Formatting
LPS-49070 remove unthrown exception
LPS-49070 *Filter is for servlet filters. *PortletFilter is for portlet filters. See CheckboxParametersPortletFilter
LPS-49070 I generally use "request" because that's the jsp implicit var. But there isn't one for wrapper, so I just all it the full var name. See usage in PortalImpl
LPS-49425 update ES impl of pagination
LPS-49425 rename poorly named test
LPS-49425 SF
LPS-49425 Simplify?
LPS-49425 SF
LPS-49425 SF
Test Fixes - CPSharepoint - tests
LPS-35593 Fix detected issue. The reference to the page should be updated
LPS-49147 Remove abstract from BaseDLFileEntryActionsDisplayContext so that we don't forget to implement all the methods in the interface by just delegating to our parent. This will allow overriders to just override the methods they are interested in without needing to worry about implementing the full DLFileEntryActionsDisplayContext interface. Also, it will allow overriders to be forward compatible when the DLFileEntryActionsDisplayContext changes by declaring more methods.
LPS-49147 Prevent DefaultDLFileEntryActionsDisplayContext from extending BaseDLFileEntryActionsDisplayContext. This is to avoid forgetting some method implementations when we add more methods to DLFileEntryActionsDisplayContext. As BaseDLFileEntryActionsDisplayContext is designed for external overriders, it lets extenders to only implement methods by cherry picking, delegating the rest to the parent DLFileEntryActionsDisplayContext. This is not ideal for DefaultDLFileEntryActionsDisplayContext because it has not parent DLFileEntryActionsDisplayContext, so it's safer not to extend the BaseDLFileEntryActionsDisplayContext.
LPS-49147 Avoid wrapping DLFileEntryActionsDisplayContext with overriders when there's no fileEntry available. This is to simplify life of overriders, but it is also possible that we need to remove this if in the future (for newly created file entries).