Migrate to JSpecify annotations

[sh-cho]

(Base: #6457)

Motivation:
jsr-305 is dormant and now JSpecify is recommended annotation sets for variety of static analyses (for now, it supports only nullness) and many open sources are moving to JSpecify (e.g. Spring Framework, Guava, ...)

• https://jspecify.dev/
• https://spring.io/blog/2025/03/10/null-safety-in-spring-apps-with-jspecify-and-null-away

Modifications:

• Add JSpecify dependency
• Deprecate internal annotations and replace to JSpecify annotations
  • com.linecorp.armeria.common.annotation.Nullable -> org.jspecify.annotations.Nullable
  • com.linecorp.armeria.common.annotation.NonNullByDefault -> org.jspecify.annotations.NullMarked

Note:
Since JSpecify's Nullable annotation is type-use annotation, placement of existing jsr-305 annotations are incompatible with JSpecify one, so following steps should be applied (ref: https://jspecify.dev/docs/using/#if-your-code-already-uses-jsr-305-annotations)

• @Nullable Object[] -> Object @Nullable []
• @Nullable Map.Entry<K, V> -> Map.@Nullable Entry<K, V>

Result:

• Resolves Use JetBrains's Java annotations? #2793
• jsr-305 annotations are migrated

[github-actions]

🔍 Build Scan® (commit: 44a902f)

Job name	Status	Build Scan®
build-ubicloud-standard-16-jdk-8	❌ (failure)	https://ge.armeria.dev/s/7xqzg4cv7eo7o
build-ubicloud-standard-16-jdk-25	✅	https://ge.armeria.dev/s/t3czmvo4sfini
build-ubicloud-standard-16-jdk-21-snapshot-blockhound	✅	https://ge.armeria.dev/s/m5nrv3iticmfc
build-ubicloud-standard-16-jdk-17-min-java-17-coverage	✅	https://ge.armeria.dev/s/qyt5kfg6wiui6
build-ubicloud-standard-16-jdk-17-min-java-11	✅	https://ge.armeria.dev/s/3rcke5sh33taw
build-ubicloud-standard-16-jdk-17-leak	✅	https://ge.armeria.dev/s/v433owzfvvwni
build-ubicloud-standard-16-jdk-11	✅	https://ge.armeria.dev/s/vabbo5f7dlzgm
build-macos-latest-jdk-25	✅	https://ge.armeria.dev/s/y2prkr7p6v2jo

[sh-cho]

Need to sort out commits
-> rebase done

[sh-cho]

I'll open this after #6457 gets merged and rebased

[coderabbitai]

Important

Review skipped

Too many files!

150 files out of 300 files are above the max files limit of 150.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.32%. Comparing base (8150425) to head (44a902f).
⚠️ Report is 411 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #6456      +/-   ##
============================================
- Coverage     74.46%   74.32%   -0.14%     
- Complexity    22234    23625    +1391     
============================================
  Files          1963     2120     +157     
  Lines         82437    88364    +5927     
  Branches      10764    11556     +792     
============================================
+ Hits          61385    65679    +4294     
- Misses        15918    17169    +1251     
- Partials       5134     5516     +382     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jrhee17]

👍 👍

[minwoox]

Thanks, @sh-cho!

[minwoox]

It seems like it doesn't work on JDK 8:
https://github.com/jspecify/jspecify/wiki/version-compatibility

I think we probably need to wait until we drop support for JDK 8.