[3.1.2 Backport] Cannot update db config from implicit `_default` scope to explicit `_default` scope
Description
Trying to update a database to specify an explicit _default scope instead of an implicit one triggers the handling intended for disallowing changing scopes on a database.
This is obviously incorrect, as it prevents being able to move from a non-collection aware database to one that contains a named collection inside the _default scope.
Workaround until fix: Delete and recreate the database with an explicit `_default` scope:
Trying to update a database to specify an explicit
_defaultscope instead of an implicit one triggers the handling intended for disallowing changing scopes on a database.This is obviously incorrect, as it prevents being able to move from a non-collection aware database to one that contains a named collection inside the _default scope.
Workaround until fix: Delete and recreate the database with an explicit `_default` scope: