Convert to IMPORT instead of PACKAGE

[jmle]

Fixes konveyor/analyzer-lsp#413

[github-actions]

Overall success rate: 80.25% (1897/2364)

[shawn-hurley]

We need to make sure that this does cause other issues, like finding matches when it shouldn't.

This was the initial reason to move to the package. IDK did how to do this systematically, but @pranavgaikwad did some great work putting it together.

If this solves this, I will be happy, but did want to make sure that we don't flip-flop issues :)

[jmle]

@shawn-hurley PACKAGE seems to work fine when looking for packages exclusively, but we have stuff like this in the ruleset:

    - java.referenced:
        location: PACKAGE
        pattern: java.net.(Socket|MulticastSocket|DatagramSocket|InetSocketAddress)*

which doesn't make sense, since the reference is simply not a package, but a class. IMPORT, on the other hand, seems to work for both packages and classes.

[jmle]

@shawn-hurley ...aaand then I just found this rule, which doesn't work with IMPORT but does with PACKAGE...

    - java.referenced:
        location: IMPORT
        pattern: javax.enterprise.deploy*

I'm thinking it could be worth issuing both an IMPORT and PACKAGE search whenever there is one of them, to be able we capture everything

[shawn-hurley]

I think that, for now, we take this as is; IF we find more and more where it becomes a problem, I think we open a new one and figure out how to do both and then make sure that we can filter out the results that shouldn't match.

[jmle]

I have merged it, although I guess that we'll have to see whether we want to keep using the shim for making changes in the rulesets, or if we want to change the rulesets directly instead.

[fabianvf]

I think if we can we'll want to keep making changes to the shim, since that will also help users with custom rulesets