refactor: follow storage-js

[zoedsoupe]

Problem

The project lacked support for advanced configurations and optimizations for file handling, bucket attributes, and operational flexibility. Documentation was incomplete or unclear in some areas, leading to potential misuse or inefficiencies. The transform_options functionality required modularity to support advanced transformations.

Solution

• Workflows:

  • Introduced static-analysis and enhanced caching in CI workflows.
  • Updated the Elixir version for linting to 1.17.0 for consistency with best practices.

• Enhancements to the File Module:

  • Added support for advanced configurations such as transform_options.
  • Improved modularity for handling file transformations, making it more extendable and user-friendly.

• Bucket Handling:

  • Introduced attributes such as file_size_limit and allowed_mime_types in Supabase.Storage.Bucket.
  • Modularized options and configurations for better flexibility and extensibility.

• Documentation Improvements:

  • Enhanced module-level and inline documentation across all updated modules.
  • Provided clearer examples for File, Bucket, and Object operations, ensuring users understand new and existing features.

• Transform Options:

  • Modularized transform_options to handle complex transformations in a more structured and extensible manner.
  • Added validation and parsing mechanisms for transformation-related options.

• Refactoring:

  • Simplified and modularized Supabase.Storage.Bucket, File, and related modules to ensure clean and maintainable code.
  • Improved the ObjectOptions and SearchOptions modules for better handling of object-related configurations.

Rationale

These changes were implemented to:

1. Align the project with Supabase's evolving API and Elixir best practices.
2. Enhance the functionality and scalability of the library by adding support for advanced features like transform_options and new bucket configurations.
3. Improve the user experience with comprehensive documentation and better modularity.
4. Ensure long-term maintainability and scalability through cleaner, more extensible code structures.
5. Provide robust workflows for quality assurance and seamless integration in CI pipelines.