🤖 I have created a release *beep* *boop*
---


### Updating meta-information for bleeding-edge SNAPSHOT release.

---
This PR was generated with [Release Please](https://togithub.com/googleapis/release-please). See [documentation](https://togithub.com/googleapis/release-please#release-please).

…to v2.19.0 (#1910)

* chore(deps): update dependency com.google.cloud:google-cloud-storage to v2.19.0

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

Update native-image related config to be specific for this class.

Update maven config to explicitly configure this new class as its only class for test when run under -Pnative

…1911)

This should fix release script reporting back to the release PRs
Source-Link: googleapis/synthtool@4c15ec0
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-java:latest@sha256:e62f3ea524b11c1cd6ff7f80362736d86c0056631346b5b106a421686fce2726

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

…0215524 (#1917)

When b/270215524 is fixed and rolled out we should be able to revert this

…9.0 (#1914)

* chore(deps): update dependency com.google.cloud:libraries-bom to v26.9.0

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

* test(deps): update cross product test dependencies

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

GCS Supports negative offsets in ranged reads and is documented in https://cloud.google.com/storage/docs/json_api/v1/parameters#range

Update the ReadChannel returned from Storage.reader to allow providing a negative value to `seek`.

NOTE: `seek` to a negative offset will be ignored by GCS if `limit` is also specified

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>