Improve interaction with typetools checker-qual dependency

[wmdietl]

In EISOP we have a few small changes to the annotations in checker-qual, in particular DefaultQualifier has the additional applyToSubpackages attribute.

When directly depending on the artifacts, it should be easy to keep the dependencies in sync.
But e.g. when trying to combine NullAway with EISOP, one can run into an exception like this:

error: Error when invoking constructor org.checkerframework.checker.nullness.KeyForAnnotatedTypeFactory(class org.checkerframework.common.basetype.BaseTypeChecker) on args [org.checkerframework.checker.nullness.KeyForSubchecker@61a6bcfa]; cause: TreeUtils.getMethod(org.checkerframework.framework.qual.DefaultQualifier, applyToSubpackages, 0): expected 1 match, found 0: []
  ; The Checker Framework crashed.  Please report the crash.  Version: Checker Framework 3.42.0-eisop5. 
  Checker: class org.checkerframework.checker.nullness.NullnessChecker
  Exception: org.checkerframework.javacutil.BugInCF: TreeUtils.getMethod(org.checkerframework.framework.qual.DefaultQualifier, applyToSubpackages, 0): expected 1 match, found 0: []; org.checkerframework.javacutil.BugInCF: TreeUtils.getMethod(org.checkerframework.framework.qual.DefaultQualifier, applyToSubpackages, 0): expected 1 match, found 0: []
  	at org.checkerframework.javacutil.TreeUtils.getMethod(TreeUtils.java:1248)
  	at org.checkerframework.javacutil.TreeUtils.getMethod(TreeUtils.java:1223)
  	at org.checkerframework.framework.util.defaults.QualifierDefaults.<init>(QualifierDefaults.java:200)
  	at org.checkerframework.framework.type.GenericAnnotatedTypeFactory.createQualifierDefaults(GenericAnnotatedTypeFactory.java:800)
  	at org.checkerframework.framework.type.GenericAnnotatedTypeFactory.createAndInitQualifierDefaults(GenericAnnotatedTypeFactory.java:786)

Tasks:

• Write an example that shows how to successfully use EP + NullAway + EISOP together in a project
• Write a test case that has an invalid combination of typetools checker-qual and eisop checker, illustrating the crash
• More gracefully handle the situation. If the applyToSubpackages attribute isn't there, issue a note to the user and continue without the feature.