Move builder activation to builder_enabled flag

1. Remove builder_enabled box toggle, via #10067
2. Add builder_enabled to Organization model, and set NOT NULL, via #10188
3. Disable builder FF for users with disabled builder. In the box create a listing Carto::User.where(builder_enabled: false).select(&:builder_enabled?) and disable flag in Central.
4. Start accepting builder_enabled updates from Central, via #10190
5. Copy the values from FF, Carto::User.find_each { |u| u.update_column(:builder_enabled, u.builder_enabled?) } (this will disable the builder for anyone who doesn’t have the FF set).
6. Update User model functions to stop reading the FF and just check the attribute instead, via #10189
7. Make Central stop setting the FF (now it is being copied from the attribute on save). via CartoDB/cartodb-central#1530
8. Remove feature flag

Note: Currently builder_enabled? is a method that checks the FF, builder_enabled is the attribute.

[javitonino]

• Just from the UI. Yes, we want Central to be the authoritative source for builder_enabled, not the user. And we are not syncing from the box to central. So I think the best way is to disable the option to change this before syncing.
• That code snippet is setting builder_enabled attribute from the feature flag (which is builder_enabled? ending in ?).

And you are right about that steps, that is roughly the idea.

[juanignaciosl]

🐔

(just kidding)