Fix default value of civicrm_option_group.is_locked in DB schema

[eileenmcnaughton]

Overview
The 5.5 update set civicrm_option_group.is_locked & is_reserved to have a db defaults but the upgrade script was incorrect on is_locked

Before
Newly created option groups (e.g for custom fields) are set to is_locked

After
Newly created option groups (e.g for custom fields) are not set to is_locked

Technical Details
The default for new instals was correct

Comments
@seamuslee001

[totten]

Thinking about how this gets cleaned up on sites. We could document a procedure for using SQL to inspect the option-groups and update is_locked on a handful?

Or what about adding this query to the upgrade script:

UPDATE civicrm_option_group SET is_locked = 1 WHERE name regexp '.*_2018[0-9]+$';

To wit: for any option-groups which look like user-generated ones from 2018 (b/c it ends with _2019nnnnnnnn), switch off the lock. It's not perfect... we could concoct a scenario where this cleanup flubs something. But it seems like a decent default behavior. Open to better ideas.