Settings in Part Definitions

⚠️ This is a very small change which might affect existing databases.

The settings property of the part definition object has been removed as it was not used. In fact, it has long been superseded by the settings property in the backend profile. This also has the advantage of differentiating settings according to the part role.

If an existing database was created before this change, it will have this redundant settings property in the facets collection. This will produce an error in the API, because it does not know how to deserialize this from the database. To fix this, just execute this command to delete all the settings properties from all the part definitions of facets:

db.facets.updateMany({}, { $unset: { "partDefinitions.$[].settings": "" } });