Enhance record batch API with UTF8 and date/time support

[yogendra-17]

Pull Request description

Draft. Extends IRX Arrow C++ record batch bridge with:

• String columns: utf8, large_utf8.
• Temporal columns: date32, date64, time32(s|ms), time64(us|ns), timestamp(s|ms|us|ns).

Files:

• packages/irx/src/irx/builder/runtime/arrow/native/irx_record_batch.{h,cpp} — native builders/getters.
• packages/irx/src/irx/builder/runtime/record_batch.py — registry.
• packages/irx/src/irx/record_batch.py — high-level API + _date_to_int / _datetime_to_int / _time_to_int
  helpers.
• packages/irx/tests/test_record_batch.py — tests.

Note: Overlaps with open PR #93 until it merges.

How to test these changes

• pytest packages/irx/tests/test_record_batch.py -v

• ...

Pull Request checklists

This PR is a:

• bug-fix
• new feature
• maintenance

About this PR:

• it includes tests.
• the tests are executed on CI.
• the tests generate log file(s) (path).
• pre-commit hooks were executed locally.
• this PR requires a project documentation update.

Author's checklist:

• I have reviewed the changes and it contains no misspelling.
• The code is well commented, especially in the parts that contain more
  complexity.
• New and old tests passed locally.

Additional information

Reviewer's checklist

Copy and paste this template for your review's note:

## Reviewer's Checklist

- [ ] I managed to reproduce the problem locally from the `main` branch
- [ ] I managed to test the new changes locally
- [ ] I confirm that the issues mentioned were fixed/resolved .

[yuvimittal]

If v overflows int32_t (e.g. a millisecond-epoch value passed by mistake) data is silently corrupted. Add a bounds check: if (v < INT32_MIN || v > INT32_MAX) return set_err("value out of int32 range", IRX_ERR_OOB); before the cast.

[yuvimittal]

Same silent narrowing issue as in append_date. Needs the same overflow guard.

[yuvimittal]

@yogendra-17 , thanks for working on this