feat: Resumable uploads

[juancarlospaco]

What kind of change does this PR introduce?

• Resumable uploads feature.

[bogdanteleaga]

Will this be merged anytime soon? Experiencing some problems with regular uploads from some instances and this has been suggested as a possible fix in a ticket.

[silentworks]

I've finally gotten around to reviewing this and there are a few things I think we should change here.

• The API seems too verbose and requires too many steps to start uploading when compared to https://github.com/tus/tus-py-client or even https://github.com/tus/tus-js-client.
• I have tested this with local Supabase (and this will probably be the same with self-hosted) and the TUS implementation in these environments don't return an upload-expires header and this is not implemented in any of the other TUS clients I've looked at so we should probably not have this either
• In the tests you are checking if a url is https, not sure if this is a requirement for uploads as local Supabase doesn't have TLS enabled by default

[silentworks]

After having a chat with @grdsdev, I think this PR should be put on hold for now. It diverges from the other Supabase client libraries and we should probably wait for an API design to be agreed upon before including resumable uploads into the Python library itself. In the time being we can add example code to the docs https://supabase.com/docs/guides/storage/uploads/resumable-uploads?queryGroups=language&language=js where Resumable uploads is mentioned using one of the third party libraries available for TUS with Python.

[silentworks]

I've opened a PR with example code for tus-py-client in the docs supabase/supabase#32517 and I've also created a repo with a working example of this https://github.com/silentworks/supabase-tus-upload-examples