Update from upstream SwiftPhoenixClient

[grdsdev]

What kind of change does this PR introduce?

Bug fix, feature, docs update, ...

What is the current behavior?

Please link any relevant issues here.

What is the new behavior?

Feel free to include screenshots if it includes visual changes.

Additional context

Add any other context or screenshots.

[foodisbeast]

Looks great, could use this now! Any idea on when this will be merged / released?

[foodisbeast]

I tried using this version in my project, but the latest version of supabase-swift has different initializers for RealtimeClient. I was able to enable usage by editing the initializers ( #22 ).

[foodisbeast]

Currently using latest from update-upstream with realtime Presence in my project. However could only get it working when adding custom channel params that matches RealtimeChannelOptions type from supabase-js (See RealtimeChannelOptions in supabase-js master).

export type RealtimeChannelOptions = {
  config: {
    /**
     * self option enables client to receive message it broadcast
     * ack option instructs server to acknowledge that broadcast message was received
     */
    broadcast?: { self?: boolean; ack?: boolean }
    /**
     * key option is used to track presence payload across clients
     */
    presence?: { key?: string }
  }
}

Wondering if there should be some additional config type, automatic payload injection in Presence, or I should just add docs @GRSouza?

let client = supabase.realtime
let params = [
    "config": [
        "presence": [
            "key": profile.id
        ],
        "broadcast": [
//          "ack": true
            "self": true
        ]
    ]
]
// let channel = client.channel(.table(id, schema: "someChannel") - presence.onSync will never call
let channel = client.channel(.table(id, schema: "someChannel"), params: params) // This works fine
let presence = Presence(channel: channel)
presence.onSync {
    // Only calls if params are passed into channel
}
client.connect()
channel.join()

[grdsdev]

@foodisbeast realtime-js automatically inject params as you can see on https://github.com/supabase/realtime-js/blob/master/src/RealtimeChannel.ts#L136-L142

I think we should use the same approach and also add documentation

[foodisbeast]

What do you think about adding a string initializer to ChannelEvent @GRSouza? Seems having a finite set of events will prevent listening/sending Presence track and untrack (Presence docs), and broadcast events (Broadcast docs).

[grdsdev]

If we can't know all the possible events then it's fine to add a string initializer @foodisbeast