Dependency should also consider parameter annotations

[uhafner]

In #171 dependencies have been enhanced to check for annotations (see also #136).
What has not been fixed in this PR is the support for annotations for parameters.

When I define the following rule:

    public static final ArchRule NO_FORBIDDEN_ANNOTATIONS_USED =
            noClasses().should().dependOnClassesThat(
                    have(type(edu.umd.cs.findbugs.annotations.CheckForNull.class)));

Then the following code will produce only a violation for the member, but not for the parameter.

@CheckForNull
public boolean exists(@CheckForNull final String fileName) {...}

It would be quite helpful if ArchUnit would also consider parameter annotations as a dependency (the types of parameters are correctly considered a dependency).

[codecholeric]

Yes, this is still a shortcoming 😞 It was not forgotten, but it is blocked by #113, i.e. we do not have the info yet, because parameter annotations are not yet imported.
But I agree that once #113 is solved parameter annotations should also be added to the dependencies.