Use same .clang-format in cuDF JNI

[bdice]

Description

Closes #15546.

Currently cuDF JNI uses its own .clang-format settings. These settings organize includes differently than the rest of the cuDF C++ codebase, so we would like to align them.

This PR removes the JNI's custom .clang-format and instead uses the same settings as the rest of cuDF.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[ttnghia]

Do we have CI style check for the java folder?

[bdice]

Do we have CI style check for the java folder?

The changes in this PR were enforced by pre-commit, so I’d say yes.

[harrism]

Thank you @bdice!

[harrism]

JNI compilation errors are due to the reordering exposing cases where files did not IWYU. e.g.

In file included from /__w/cudf/cudf/java/src/main/native/src/CompiledExpression.cpp:18:
     [exec] /__w/cudf/cudf/java/src/main/native/src/jni_compiled_expr.hpp:36:37: error: 'ast' is not a member of 'cudf'; did you mean 'cudf::jni::ast'?

This file uses libcudf AST types without a corresponding include.

[bdice]

/merge