Wrong usage of mappers factory should be able to remove static initializer

Nobody has claimed this yet.

Why reviewing PR #179 @hduelme pointed out that the Wrong usage of mappers factory does not work (i.e. it does not remove it) with the following code:

```java
@Mapper(componentModel = "spring")
abstract class WrongComponentModelMapper {

static {
Mappers.getMapper(WrongComponentModelMapper.class);
}

Target map(Target source);
}
```

or
```java
@Mapper(config = MyConfig.class, componentModel = "spring")
interface WrongComponentModelMapper {

WrongComponentModelMapper INSTANCE = () -> {
return Mappers.getMapper(WrongComponentModelMapper.class);
};

Target map(Target source);
}
```

We need to see if we can support this.

Start by reproducing the static-initializer and interface-field examples from the issue and tracing how the IntelliJ plugin currently handles Mappers.getMapper usage. Check the discussion around PR #179 for context. Done means determining whether these patterns can be supported and, if so, validating the behavior with coverage for both examples.

Written by the indexing model from the issue text.