With 3.16 we are defaulting to rendering the new react UI instead of the old angular UI. We need to give admins the option to disable access to the old UI if they are concerned about out of date packages or CVE's related to the old UI.

Because of this we require the following changes:

• Add a new DISABLE_ANGULAR_UI param, where when enabled and DEFAULT_UI is set to "react", the option to toggle back to the old UI is disabled
• Move the toggle in the new UI from the header to under the user drop down in the top right of the screen
• Update the name of the "patternly" cookie, so when users login to a Quay instance that has just deployed 3.16 it won't pick up on that cookie and automatically go to the angular UI

The following should be tested

• All screens in the old and new UI should still work correctly, given the nginx changes
• By default the params should be DEFAULT_UI=react and DISABLE_ANGULAR_UI=false, where the react UI is rendered on login with the option to toggle back
• When DEFAULT_UI=react and DISABLE_ANGULAR_UI=true only the react UI should render with no option to toggle back
• When DEFAULT_UI=angular the angular UI should render always with the option to toggle to the react UI, no matter what DISABLE_ANGULAR_UI is set too
• If the user is currently logged in to the angular UI and the Quay instance is updated with this patch, the user should be automatically sent to the new UI