Upgrade JSpecify 0.3.0 -> 1.0.0

[Picnic-DevPla-Bot]

This PR contains the following updates:

Package	Type	Update	Change
JSpecify (source)	compile	major	0.3.0 -> 1.0.0

---

Release Notes

jspecify/jspecify (JSpecify)

### [`v1.0.0`](https://togithub.com/jspecify/jspecify/releases/tag/v1.0.0): 1.0.0 [Compare Source](https://togithub.com/jspecify/jspecify/compare/v0.3.0...v1.0.0) JSpecify 1.0.0 is the first stable release of the only [consensus-driven](https://jspecify.dev/about/), tool-independent nullness annotations for Java code (with benefits for Kotlin interoperability). Future releases will add annotations for other kinds of static-analysis checks. Check out our [usage page](https://jspecify.dev/docs/using) for instructions on how to depend on JSpecify in your project and our guidelines on [when to start](https://jspecify.dev/docs/whether) doing so. Also check out our [User Guide](https://jspecify.dev/docs/user-guide). The 1.0.0 release contains four annotations: - [`@Nullable`](https://jspecify.dev/docs/api/org/jspecify/annotations/Nullable.html) - [`@NonNull`](https://jspecify.dev/docs/api/org/jspecify/annotations/NonNull.html) - [`@NullMarked`](https://jspecify.dev/docs/api/org/jspecify/annotations/NullMarked.html) - [`@NullUnmarked`](https://jspecify.dev/docs/api/org/jspecify/annotations/NullUnmarked.html) ### Artifacts - [Javadoc](https://jspecify.dev/docs/api/) - Maven Central: [org.jspecify:jspecify](https://repo.maven.apache.org/maven2/org/jspecify/jspecify/1.0.0/) ### Changes since version 0.3.0 No code changes, only Javadoc changes and OSGI metadata.

---

• [ ] If you want to rebase/retry this PR, check this box

[Picnic-DevPla-Bot]

Suggested commit message:

Upgrade JSpecify 0.3.0 -> 1.0.0 (#1256)

See:
- https://github.com/jspecify/jspecify/releases/tag/v1.0.0
- https://github.com/jspecify/jspecify/compare/v0.3.0...v1.0.0

[github-actions[bot]]

Looks good. No mutations were possible for these changes. Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions[bot]]

Looks good. No mutations were possible for these changes. Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions[bot]]

Looks good. No mutations were possible for these changes. Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions[bot]]

Looks good. No mutations were possible for these changes. Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions[bot]]

Looks good. No mutations were possible for these changes. Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions[bot]]

Looks good. No mutations were possible for these changes. Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions[bot]]

Looks good. No mutations were possible for these changes. Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions[bot]]

Looks good. No mutations were possible for these changes. Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions[bot]]

Looks good. No mutations were possible for these changes. Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions[bot]]

Looks good. No mutations were possible for these changes. Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud