Allow cookbook to pair build version with Arrow release version

As more features are added to Apache Arrow, we might want to build versions of the cookbook that are relevant to that release.

I'm not sure what a good strategy would be in terms of adding content, e.g. is the main branch the latest version, and we create branches for releases, and then cherry-pick any commits which are relevant to multiple cookbook versions? And how many versions to have, in terms of major/minor releases?

The issue names no files, tests, or entry points. First define the release and branch strategy, including which cookbook versions to maintain and how shared changes are applied. Done means the project has an agreed, documented way to pair cookbook builds with Arrow release versions.

Written by the indexing model from the issue text.