refactor: match with new supabase_potion release

[zoedsoupe]

Problem

The project lacked a consistent approach for managing bucket and object operations within Supabase Storage. There were inefficiencies in handling requests, and certain functions required clearer implementations to align with the existing Supabase standards.

Solution

1. Refactored Bucket Operations:

   • Improved the create_bucket, retrieve_bucket_info, and update_bucket methods to streamline their workflows.
   • Enhanced error handling by introducing clear cases for validation and exception management.

2. Object Management Improvements:

   • Refactored upload_object, remove_object, and list_objects for better performance and clearer logic.
   • Introduced lazy streaming for large object downloads to handle memory-efficient operations.

3. Improved Code Maintainability:

   • Consolidated duplicate logic within bucket_handler.ex and object_handler.ex.
   • Updated the usage of request builders with consistent patterns across all modules.

Rationale

The changes were implemented to:

1. Align the module's operations with Supabase's evolving API standards.
2. Improve the performance of common storage tasks like bucket creation and object retrieval.
3. Ensure easier maintainability by removing redundancies and unifying patterns in request handling.
4. Introduce robust error handling and validations for smoother user interactions and debugging.