GH-40689: [Docs] Add nanoarrow to implementation status page

[paleolimbot]

Rationale for this change

nanoarrow now supports most types and reading IPC streams. As discussed in the issue, there is interest in adding it to the implementation status page for visibility.

What changes are included in this PR?

A column was added to the table with the appropriate values characterizing the C library implementation status.

Are these changes tested?

Not needed (docs!)

Are there any user-facing changes?

No (docs!)

• GitHub Issue: [Docs] Include nanoarrow in the Implementation Status docs page #40689

[github-actions]

⚠️ GitHub issue #40689 has been automatically assigned in GitHub to PR creator.

[paleolimbot]

@github-actions crossbow submit preview-docs

[github-actions]

Only contributors can submit requests to this bot. Please ask someone from the community for help with getting the first commit in.
The Archery job run can be found at: https://github.com/apache/arrow/actions/runs/8582761059

[kou]

@github-actions crossbow submit preview-docs

[kou]

@paleolimbot Could you change your visibility to "Public" from "Private" in the "apache" organization to use @github-actions crossbow submit?
See also: https://github.com/orgs/apache/people?query=paleolimbot

[github-actions]

Revision: cb81cda

Submitted crossbow builds: ursacomputing/crossbow @ actions-8465c6de82

Task	Status
preview-docs

[ianmcook]

@paleolimbot some of these tables are getting so wide that the layout risks breaking. One easy way to improve this is to replace all JavaScript with JS in the header rows. Could you do that please?

To further minimize width, perhaps also change nanoarrow to nano in the header rows, and include this at the end of the paragraph at the top of the page:

"nano" refers to nanoarrow_.

.. _nanoarrow: https://arrow.apache.org/nanoarrow/

While you're editing this file, can you fix the two places in the tables where there's a × instead of a ✓?

[ianmcook]

I think it would also be good to add nanoarrow to the Implementations drop-down. You can add it here between MATLAB and Python:

   nanoarrow <https://arrow.apache.org/nanoarrow/>

[github-actions]

Revision: 3637c2a

Submitted crossbow builds: ursacomputing/crossbow @ actions-45d3a340b4

Task	Status
preview-docs

[paleolimbot]

@github-actions crossbow submit preview-docs

[github-actions]

Revision: 3637c2a

Submitted crossbow builds: ursacomputing/crossbow @ actions-e4736958c9

Task	Status
preview-docs

[paleolimbot]

Thank you for taking a look!

One easy way to improve this is to replace all JavaScript with JS in the header rows. Could you do that please?

Done!

I think it would also be good to add nanoarrow to the Implementations drop-down.

Done!

To further minimize width, perhaps also change nanoarrow to nano in the header rows

I don't mind doing this; however, I did check a variety of page widths and at the point where the page is on vertical mobile it already cuts off just after JavaScript. A longer term solution might be to transpose the table and repartition the features a bit rather than add another column.

[paleolimbot]

@github-actions crossbow submit preview-docs

[github-actions]

Revision: 167df74

Submitted crossbow builds: ursacomputing/crossbow @ actions-e98970d8ec

Task	Status
preview-docs

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit dbedcfc.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details.