Drop JSR305 support in favor of JSpecify
We should see what breaks if we remove "com.google.code.findbugs:jsr305"
in scope of this issue do you want just drop or replace jsr305?
We're not totally sure yet. I've added the "pending design work" label to make it clearer that we're not ready to accept contributions yet for this one.
It still breaks for the use of Spring Framework's @Nullable in a deprecated form. :module:spring-boot-health: is also failing although I wasn't able to figure out why, probably another incantation of @Nullable.
As long as Spring Framework's @Nullable is deprecated we won't be able to remove the usage of JSR 305 completely. I have requalified this issue as, in terms of documentation and code, we do not support it anymore in a non-deprecated form.