Allow Default Scope to be Locked or Dropped

We made a conscious decision to not allow Default Scope to be dropped - only Default Collection can be dropped. The reasoning was that the end-user should not need to create a scope, hence they should always have a scope to work with out-of-the-box. In contrast, the use of named collections is mandatory, and hence Default Collection is only considered a migration convenience and hence is droppable. 

However, customer is saying that they would like the Default Scope to be locked or dropped. They are worried that some developers may accidentally start writing into it. So they want to 'lock' it or drop it.

They are ok with the fact that it cannot be recreated.

Upon reconsideration this seems like a reasonable request. I researched SQL Server and PostgresSQL. SQL Server does allow 'dbo' schema to be dropped. Similarly PostgresSQL does allow Public schema to be dropped.