Fixes #1193

…#1211)

…Invocation (#1210)

### unit test: newNullableWithArg()

Generalised the parameters of getGenericParameterNullnessAtInvocation to
accept NewClassTree

Fixes #1214

---------

Co-authored-by: Manu Sridharan <[email protected]>

…1212) (#1217)

Handle NewClassTree for constructor type substitution in
compareGenericTypeParameterNullabilityForCall.

Addresses part of #1212

---------

Co-authored-by: Manu Sridharan <[email protected]>

Fixes #1219 

Previously, we would only consider the `isNotNull` method of
`org.assertj.core.api.AbstractAssert` to be valid. Now, we allow
`isNotNull` of any class that implements the
`org.assertj.core.api.Assert` interface, which handles the case from
#1219 and more.

This PR fixes the broken link to the Eradicate that has been removed in
the latest version in the `README.md`.

See https://github.com/facebook/infer/blob/main/Changelog.md#checkers

This PR changes to support AssertJ `hasSize()`.

See gh-1224

…eter passing (#1226)

…tions (#1225)

This is a new approach to serializing the annotations from
https://github.com/jspecify/jdk for use with NullAway. The idea is we
build that JDK with this plugin, which will dump out all the discovered
annotation info into JSON files. Then, we write some code to take all
those JSON files and convert them to astubx for NullAway. I went with
JSON instead of directly serializing astubx to iterate more quickly. I
have tested with jspecify/jdk and confirmed I can inject this plugin
into the build and the output JSON files get created. I haven't started
on the code to convert the JSON to astubx yet.

Of course there is much left to do, but I wanted to get this initial
implementation up for review rather than dropping a huge PR at the end
(and also to enable others to help out). We previously thought about
getting out the JDK annotations by parsing the source files (and wrote
some code to do so), but I think this approach will be more robust, as
in the javac plugin we don't need worry about parsing of recent language
features and all symbols are just resolved.

Related to #950 (which probably needs to be updated if we go forward
with this approach)

Prior to this change, NullAway could be skipped only with an explicit
`@SuppressWarnings("NullAway")` annotation. However, existing
inspections like `DataFlowIssue` by JetBrains imply that NullAway should
be skipped too.

With this change, NullAway can be configured to back off when additional
names are present, via the `SuppressionNameAliases` configuration
option.

* Closes #1230

Fixes #1218. I also updated the Shadow plugin to a more recent version,
as that often has subtle interactions with releasing.

To test, I followed the instructions at
https://github.com/vanniktech/gradle-maven-publish-plugin/releases/tag/0.33.0.
I successfully uploaded a `SNAPSHOT` release with these changes, but we
should cut a normal release after this lands to make sure that works.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Chores**
* Updated Maven Publish Gradle plugin and Shadow plugin to newer
versions.
  * Switched Shadow plugin provider to improve build configuration.
  * Updated publishing properties to enable Maven Central publishing.
  * Adjusted build tasks to use updated Javadoc JAR task names.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->