[CI][Java] Use current cookbooks projects to validate new release versions

Current there are recipes to validate Arrow components at:

There are a CI process to create components for new Arrow Java releases:

These two projects are working independently.

The purpose of this ticket is to {**}define a way about how to use cookbooks to validate new releases version{**}.

`[~jwozniak]` @raulcd @lwhite1  

**Reporter**: [David Dali Susanibar Arce](https://issues.apache.org/jira/browse/ARROW-17073) / @davisusanibar

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

Start by comparing the recipes in the apache/arrow-cookbook project with the Java release components published at the Apache Arrow Java nightly site. Define how cookbook validation should connect to new Java releases and what CI result confirms a release is validated. No specific files or tests are named in the issue.

Written by the indexing model from the issue text.