Ignoring a property based on the attribute on the property instead of the mapper attribute about mapperly

[moxplod]

My use case is for system/calculated fields. That I do not want the users to modify. But I do want to show them those fields.

[latonz]

Relates to #585. I'm not sure about configuring mappings on the entities themselves. With the current approach all configuration of the mapper is visible within its class.

[moxplod]

Yea - it is related. But in my scenario, using the current approach leads to compiler warnings as I am using MapDerivedType.

The ignored fields are only going to be present in one of the child classes.

For example, I want to ignore Risk property in the Company class. But that does not exist in Contact, that will throw a warning.

[latonz]

Currently configuration is not supported on methods using MapDerivedType (see also #910). You would need to configure the ignores on a mapping method for each mapping individually.

[latonz]

Also related to #585.