Commit 037062a2eceddc52d95742e5883a136a6e4ca67d implements this as a new property recordingRemovals (defaulting to false) which if set causes a WarningStatus to be added for each entity attribute removed.

The use case for this (including notice of filtered entity attributes in a report along with, for example, entities failing other checks) doesn't fit very well with logging as such. It makes more sense to optionally add an appropriate StatusMetadata and leave turning that into a logged message to a later StatusMetadataLoggingStage.

Another issue is whether it makes more sense to add a WarningStatus or an InfoStatus. The only similar case to date has used WarningStatus, and that's probably what we'd want for the specific use case, but it would probably be nice to have the ability to select between these options. Two boolean properties? A three-way private enum?