Branding is not taken into account in other pages than the main one

User dashboard, for instance, is still using the galaxy theme.

Options are available at this point:

1. keep on generating a theme with a custom name, and make sure all views configured to use theme galaxy (like user_dashboard page) are also overriden when building the Studio jar.

• advantages: we keep on having the galaxy theme for local conf, and users see their custom theme in local conf with their studio project name instead of "galaxy"
• drawbacks: might be a pain for maintenance of Studio + we need to warn customers that their theme override or usage in other jars must use another name than galaxy

2. back to old behaviour: the main theme overrides the one called galaxy, others are generated with their custom theme

• advantages : compatibility not broken anymore, no need to keep track in Studio of configurations referencing the galaxy theme
• drawbacks: galaxy theme is the custom one, might be confusing for local conf

In both cases, users do not have a control on the name of theme generated when it is declared as the main one, see if this is an issue.