feat(r): Add bindings to IPC writer

[paleolimbot]

This PR adds a basic level of support for IPC writing in the R package. This is basically a thin wrapper around ArrowIpcWriterWriteStream() and could be more feature-rich like the Python version (that allows schemas and batches to be written individually).

I also added a bit of code to handle interrupts (which should catch interrupts on read and write and wasn't handled before).

library(nanoarrow)
tf <- tempfile()

nycflights13::flights |> write_nanoarrow(tf)
(df <- tf |> read_nanoarrow() |> tibble::as_tibble())
#> # A tibble: 336,776 × 19
#>     year month   day dep_time sched_dep_time dep_delay arr_time sched_arr_time
#>    <int> <int> <int>    <int>          <int>     <dbl>    <int>          <int>
#>  1  2013     1     1      517            515         2      830            819
#>  2  2013     1     1      533            529         4      850            830
#>  3  2013     1     1      542            540         2      923            850
#>  4  2013     1     1      544            545        -1     1004           1022
#>  5  2013     1     1      554            600        -6      812            837
#>  6  2013     1     1      554            558        -4      740            728
#>  7  2013     1     1      555            600        -5      913            854
#>  8  2013     1     1      557            600        -3      709            723
#>  9  2013     1     1      557            600        -3      838            846
#> 10  2013     1     1      558            600        -2      753            745
#> # ℹ 336,766 more rows
#> # ℹ 11 more variables: arr_delay <dbl>, carrier <chr>, flight <int>,
#> #   tailnum <chr>, origin <chr>, dest <chr>, air_time <dbl>, distance <dbl>,
#> #   hour <dbl>, minute <dbl>, time_hour <dttm>
identical(df, nycflights13::flights)
#> [1] TRUE

^{Created on 2024-09-14 with reprex v2.1.1}

[amoeba]

Looks good to me. Left some notes, feel free to ignore or open separate issues. I'll note that I couldn't do a thorough job reviewing the C parts of this.

[amoeba]

This puts write_nanoarrow on read_nanoarrow's page which either needs to be updated or maybe write_nanoarrow just needs its own help page. I'm happy to contribute the latter.

[paleolimbot]

I added a basic level of inclusion on the read page but feel free to contribute something better!

[amoeba]

where does the 16MB value come from?

[paleolimbot]

I added a note about this...it's somewhere between a big value (to reduce the number of R calls) and a small value (to minimize the copying/ensure there's an R call every once in a while to catch an interrupt).

[amoeba]

Could a more useful error message be produced here? It looks like code is an errno-style error so it seems like it'd be possible.

[paleolimbot]

I added the errno value! Pretty much all that can happen here is a failure to allocate (rare, since it's a few bytes). I never quite got to adding a macro like ERROR_NOT_OK() to help with this.