Follow-up to #3572. Removing the is_default field will break the dashboard pages for any branches that do not yet have the new dashboard changes merged in. As such, this change should be done in a separate PR to avoid conflicts.

We might want to keep the is_default value in the database until we are sure that the migration and functionality works as intended.