Fix: CheckerFramework version bump

[byd110]

The CF version bump #349 fails at the test to compute the greatest lower bound and lowest upper bound. Consider the code snippet:

Problem Description

class test<T extends @AllowedAlgorithms({"a", "b"}) String> {}

void m() {
        test<? extends @AllowedAlgorithms({"a", "c"}) String> f1 = new test<>();
}

Here the object creation should be valid if we compute the lub as @AllowedAlgorithms({"a"}) String. However, in the handling before 3.43.0 release is that it takes the upper bound at class decl directly, which is @AllowedAlgorithms({"a", "b"}. Hence, here was expected an assignment.type.incompatible error before.

Solution

By removing this type of error specifications, and adapt the change of CF APIs (some signatures changed from BaseTypeChecker to SourceChecker), the build succeed.

[byd110]

add new test cases to test that extends "c" is rejected.

[wmdietl]

Thanks for tracking down the version update problems!

[wmdietl]

For the removed errors, can you instead say what the effective bound is?
I think it's fine that we no longer get the assignment errors, but the effective bounds should still give us the desired behavior. Is that the case?

[wmdietl]

I think these can be removed, as nobody uses the variables.

[wmdietl]

Can you look for all uses of the version string and update them together?