Automatically inject options into Channel

[foodisbeast]

What kind of change does this PR introduce?

feature, add docs

What is the current behavior?

Channel initializer has parameter params of type [String:Any]. When params is unset this prevents channel Presence from receiving sync events. See my earlier comment in discussion #21 for more details.

What is the new behavior?

Channel initializer has new parameter options of type ChannelOptions allowing Presence to receive sync events by default.

Additional context

ChannelOptions was generated using types found in RealtimeChannelOptions

[grdsdev]

should we really deprecate this?

aren't there other params that can be passed other than ChannelOption? Having this raw [String: Any] I think is still valid.

I'm not sure about this because I'm not used to the realtime feature, what do you think @foodisbeast ?

[foodisbeast]

Unless this package is meant to support Phoenix realtime generally, supabase realtime or realtime-js library only has these options available for initializing a channel (See RealtimeChannelOptions from realtime-js), as well as their documention for realtime only makes mention/use of RealtimeChannelOptions once when talking about Presence Key

import { createClient } from '@supabase/supabase-js'

const channelC = supabase.channel('test', {
  config: {
    presence: {
      key: 'userId-123',
    },
  },
})