CB

Currently both are being ordered by profile view position and ordering in addition to their view specific ordering. This is due to the initial defaults being all set the same so that their ordering would match profile view by default. However now that you can order all 3 views independantly within CB > Tab Management this isn't necessary anymore, but before the query can be fixed in _getTabsDb the defaults need to also be fixed (and probably migration to handle the duplicate ordering values).