Bump Pyarrow version to include 14.0.0

[AnandInguva]

Please add a meaningful description for your change here

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[AnandInguva]

Errors I see in https://github.com/apache/beam/actions/runs/7010246192/job/19070396821?pr=29536

self = <apache_beam.io.parquetio_test.TestParquet testMethod=test_sink_transform_int96>

    def test_sink_transform_int96(self):
      with tempfile.NamedTemporaryFile() as dst:
        path = dst.name
        # pylint: disable=c-extension-no-member
        with self.assertRaises(pl.ArrowInvalid):
          # Should throw an error "ArrowInvalid: Casting from timestamp[ns] to
          # timestamp[us] would lose data"
          with TestPipeline() as p:
>           _ = p \
            | Create(self.RECORDS) \
            | WriteToParquet(
                path, self.SCHEMA96, num_shards=1, shard_name_template='')
E           AssertionError: ArrowInvalid not raised

The above test fail could be because of apache/arrow#35656

---

Windows tests are running for very long time -https://github.com/apache/beam/actions/runs/7010335606/job/19070644422?pr=29536. This might be due to pyarrow update.

C:\arrow\cpp\src\arrow\filesystem\s3fs.cc:2904:  arrow::fs::FinalizeS3 was not called even though S3 was initialized.  This could lead to a segmentation fault at exit

[AnandInguva]

#28437 (comment) - following up on the comment here, I will be skipping updates for windows.

[AnandInguva]

R: @tvalentyn

[github-actions]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control

[tvalentyn]

Thanks!