shared config enhancement

Nobody has claimed this yet.

I have tried the change #1979 & it is a great improvement but still not enough & not in current release 1.3.1. I would suggest to further enhance it by allowing wildcard approach. and/or type based one. Also multiple field ignore should be allowed in Mapping instead of add one for each field. For example,

```java
class A {
private B b1;
private B b2;
private D d;
}

class AA {
private BB b1;
private BB b2;
}

class B {
private String str;
private C c1;
private C c2;
// any fields primitive or otherwise
}

class BB {
private String str;
private CC c1;
private CC c2;
// any fields primitive or otherwise
}

class C {
private String str1;
private String str2;
}

class CC {
private String str1;
private String str2;
}

class D {
private String str;
}

interface AMapper {
// wild card approach
@Mapping(target = {"*.[str1]","*.*.[str1,str2]"}, ignore=true)
// type based
@Mapping(target = {"Class[B,D].(str1)","Class[B].Class[C].(str1,str2)"}, ignore=true)
AA toAA(A a);
}
```

Start by reading issue #1979 and the current Mapping annotation/API behavior. The proposal needs an agreed design for wildcard targets, type-based selection, and multiple ignored fields before implementation can begin; done would require defined syntax and behavior for each case.

Written by the indexing model from the issue text.