MatchError on update_access_token/2 prevents supabase authentication

[zoedsoupe]

Bug report

Describe the bug

the Supabase.GoTrue.Plug or Supabase.GoTrue.LiveView modules injects a bunch of convenience functions to leverage the Plug and LiveView aiming to provide a higher level api to integrate supabase authentication with these frameworks.

after issuing the session into supabase and returning it to the sdk, it tried to update the current scope access token for the client informed in the configuration, using the Supabase.Client.update_access_token/2 function, which used to return only :ok but now return the updated %Supabase.Client{}, that leads to a MatchError preventing to authenticate with those modules.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. use either Supabase.GoTrue.Plug or Supabase.GoTrue.LiveView modules
2. get your supabase elixir client instance
3. call any of log_in_with_*/2 or hooks (if live view) with sign in parameters
4. get the MatchError while updating the current access token from the client

Expected behavior

Supabase.GoTrue.Plug and Supabase.GoTrue.LiveView injected functions should create a new supabase session

Screenshots

Additional context

Bug caught from a open source project that i manage and actively uses supabase elixir sdk, @peapescarte