[Release][Java] Verify staged maven artifacts

We have two tests right now:
1. Execute `mvn test` from the source tarball's java directory testing the source https://github.com/apache/arrow/blob/master/dev/release/verify-release-candidate.sh#L278
2. Verify the checksums and signatures of the uploaded maven artifacts https://github.com/apache/arrow/blob/master/dev/release/verify-release-candidate.sh#L766

But we don't actually **test** the packages. We should add that to the verification scripts, since 7.0 is going to be the first release shipping the jars with bundled JNI libraries.

cc @kou @anthonylouisbsb

**Reporter**: [Krisztian Szucs](https://issues.apache.org/jira/browse/ARROW-15486) / @kszucs
#### Related issues:
- [[Release][Java] Add missing files to list of artifacts to deploy](https://github.com/apache/arrow/issues/31193) (relates to)
#### Original Issue Attachments:
- [image-2022-02-18-07-07-45-928.png](https://issues.apache.org/jira/secure/attachment/13040235/image-2022-02-18-07-07-45-928.png)
#### PRs and other links:
- [GitHub Pull Request apache/arrow#148](https://github.com/apache/arrow-cookbook/pull/148)

_{**Note**: *This issue was originally created as [ARROW-15486](https://issues.apache.org/jira/browse/ARROW-15486). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*}

Empieza por dev/release/verify-release-candidate.sh, especialmente por la prueba existente de Java para el source-tarball y los pasos de verificación de artefactos de Maven. Revisa cómo se ejecuta `mvn test` desde el directorio Java del source-tarball y cómo se comprueban las sumas de comprobación y las firmas. Se considera terminado cuando los scripts de verificación también prueben los paquetes de Maven, incluidos los jars con bibliotecas JNI integradas.

Escrito por el modelo de indexación a partir del texto del issue.