feat: Use cupertino http and websocket implementation

[Vinzent03]

What kind of change does this PR introduce?

feature

What is the current behavior?

Uses the implementation from dart:io for http.Client and WebSocketChannel.

What is the new behavior?

Use the classes provided by cupertino_http.

Additional context

I do not own a mac, so I cannot test this. So we can hopefully find a person to verify this actually works on iOS and macOS.

close #147

[coveralls]

Pull Request Test Coverage Report for Build 14870387715

Details

• 12 of 27 (44.44%) changed or added relevant lines in 4 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.2%) to 75.111%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
packages/supabase_flutter/lib/src/supabase.dart	3	6	50.0%
packages/supabase/lib/src/realtime_client_options.dart	0	6	0.0%
packages/supabase_flutter/lib/src/platform_http_io.dart	8	14	57.14%

Totals
Change from base Build 14868379526:	-0.2%
Covered Lines:	2882
Relevant Lines:	3837

---

💛 - Coveralls

[grdsdev]

@Vinzent03 we should make sure we run CI also on macOS, and test the package at least in a iOS build, just saw that we don't to that.

I created an issue for tracking that, #1146 feel free to pick it if you want, otherwise I can work on it later.

[Vinzent03]

I'm pretty sure to verify the behavior of the cupertino http client we can't just run the existing ci on a macos build in ci. For iOS we need flutter integration tests to actually run them on a iOS simulator. For macOS I'm unsure if the cupertino http client works if we run widget tests or actually need integratino tests as well. So we would need to write many additional tests sa well.

[grdsdev]

I see there is an examples folder in https://github.com/supabase/supabase-flutter/tree/main/packages/supabase_flutter/example

Probably just getting all these examples built in CI, would already solve the issue with checking if the library works on all available platforms.

[grdsdev]

Hey @Vinzent03 I just merged a few changes to CI, including builds on the macOS runner, can you rebase this PR?

[Vinzent03]

I think I could get this pr working, but (with the weird error on macos now as well) I'm unsure we really want this pr to land. I think one huge benefit of the supabase packages is the lack of native dependencies, unlike firebase. So the building is a lot let stressful. We already see some supabase unrelated issues because of app_links and its native part.

Since one can already replace the http client, I think it's a better and more composable implementation to allow a custom websocket client in supabase and supabase_flutter to be passed to realtime_client. And publish a guide on how to provide the native http clients. This also means less depencency managment for us. This way the first experience is easier with no native dependency stress, but if a user wants the native clients they can easily add them.
What do you think @dshukertjr @DanMossa

[DanMossa]

Big fan of just writing a quick example for others to use.