TPT-3391: Added distinction between Object Storage Bucket Access POST/PUT endpoints

[ezilber-akamai]

📝 Description

Added ModifyObjectStorageBucketAccess struct and swapped it with UpdateObjectStorageBucketAccess such that Modify is for the POST endpoint and Update is for the PUT endpoint to avoid confusion.

As of right now, both endpoints do the same exact thing but we want separate structs in case this changes in the future.

✔️ How to Test

make test-unit
make test-int

[Copilot]

Pull request overview

This PR clarifies the distinction between the Object Storage Bucket Access POST vs PUT endpoints by introducing a dedicated “modify” API (POST) while updating the existing “update” API to use PUT, and adjusts unit/integration coverage + fixtures accordingly.

Changes:

• Added ModifyObjectStorageBucketAccess + ObjectStorageBucketModifyAccessOptions for the POST /access endpoint.
• Switched UpdateObjectStorageBucketAccess from POST to PUT and added a doPUTRequestNoResponseBody helper.
• Updated unit/integration tests and recorded fixtures to reflect the POST (modify) vs PUT (update) split.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
object_storage_buckets.go	Adds Modify (POST) access API/options and changes Update to PUT.
request_helpers.go	Adds doPUTRequestNoResponseBody helper used by the PUT update path.
test/unit/object_storage_bucket_test.go	Adds Modify-access unit test and updates Update-access to expect PUT.
test/integration/object_storage_buckets_test.go	Adds Modify-access integration test alongside Update-access test.
test/integration/fixtures/TestObjectStorageBucket_Access_Modify.yaml	New fixture capturing POST modify interaction sequence.
test/integration/fixtures/TestObjectStorageBucket_Access_Update.yaml	Updates fixture to reflect PUT update interaction.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.