refactor: Remove org.jetbrains.annotations imports

[yihua]

Describe the issue this Pull Request addresses

Closes #17678. This PR removes org.jetbrains.annotations imports that cause issues.

Summary and Changelog

This PR replaces org.jetbrains.annotations usage with javax.annotation instead.

Impact

Refactoring

Risk Level

none

Documentation Update

none

Contributor's checklist

• Read through contributor's guide
• Enough context is provided in the sections above
• Adequate tests were added if applicable

[yihua]

@voonhous could you help review this refactoring PR?

[hudi-bot]

CI report:

• 54cd00b Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

• @hudi-bot run azure re-run the last Azure build

[voonhous]

Since we've migrated to Lombok, should we use lombok.NonNull instead?

Should we also take the chance to standardise the @VisibleForTesting usages, we are mainly using:

• org.apache.hudi.common.util.VisibleForTesting

But i see references to:

• org.apache.flink.annotation.VisibleForTesting
• com.google.common.annotations.VisibleForTesting

[yihua]

Since we've migrated to Lombok, should we use lombok.NonNull instead?

On a second thought, lombok.NonNull generates runtime null-checks which is different from current behavior of static analysis. So I think for this particular PR to unblock Spark 4.1 integration, we should stick to javax.annotation.Nonnull which is consistent across the code base.

Should we also take the chance to standardise the @VisibleForTesting usages, we are mainly using:

• org.apache.hudi.common.util.VisibleForTesting

But i see references to:

• org.apache.flink.annotation.VisibleForTesting
• com.google.common.annotations.VisibleForTesting

We should do a separate sweep, #17688 to track.

[voonhous]

LGTM