Expose memory tracking API to Array and ArrayData

[waynexia]

Which issue does this PR close?

We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax.

• Follow up of memory tracking with memory pool #7303

Rationale for this change

#7303 implements the fundamental symbols for tracking memory. This patch exposes those APIs to a higher level Array and ArrayData.

What changes are included in this PR?

New APIs claim for Array and ArrayData. New feature pool to arrow, arrow-array and arrow-data for the new API

Are these changes tested?

Yes, and there is an example to demo basic usage.

Are there any user-facing changes?

New API and feature

[alamb]

Thanks @waynexia -- is there a high level description / "[EPIC]" style ticket of what we are doing with these APIs? I think it would be good to make an issue that describes the high level project / direction for wider visibility (and likely to get other people involved)

I found some related issues. Do any of them reflect your plan?

• [DISSCUSSION] the memory tracking approach that better handles shared buffers #6439
• Add a feature to allow creating Buffers from Vec with custom allocators (allocator_api) #3960