This involves a few notable changes:

It splits up our bottom drawer component into 2 parts:

• OcBottomDrawer is now deprived of almost all its logic and only handles the visual representation of the drawer. This component is meant to be used from the outside (e.g. by the right sidebar).
• OcMobileDrop contains all the logic that is heavily bound to our OcDrop component. For that reason, it is not being exposed to the outside.

Furthermore, this change refactors the panels of the SideBar component into its own component SideBarPanels. At first I thought this was necessary. It turned out that wasn't the case, but I still think it's better this way. The SideBar component now mainly handles the logic of deciding whether to display the sidebar on the right side or in a bottom drawer.

The implementation besides that it pretty straight forward, though 2 edge cases might be notable because they differ from the right sidebar behavior on the desktop view:

• When loading the page initially, we don't want the bottom drawer to show. The new method onInitialLoad of the useSidebar composable gets called once after Web has been bootstrapped and sets the sidebar open state to false on mobile. The only exception to this is when explicitly calling for the sidebar via the details query param.
• There are certain scenarios where we probably want to close the bottom drawer after the user took action. The implementation specifically checks if a link or an action of the sidebar action panel has been clicked and closes the drawer if so.

closes #1589