fix: Handle properly jwt tokens

[filipecabaco]

What kind of change does this PR introduce?

Handle properly jwt tokens as currently we were using only the apikey and that is not enough for scenarios with RLS policies.

[w3b6x9]

@filipecabaco what's the distinction between the tokens? How is Realtime server gonna use either?

[chasers]

Oh also need to do this in the Broadcast POST!

[chasers]

API Gateway requires anon or service role for the apikey.

[filipecabaco]

What @chasers said. We need to emulate the following request:

const response = await fetch(channelUrl, {
      method: "POST",
      headers: {
        "Content-Type": "application/json",
        Authorization: `Bearer ${session?.access_token!}`,
        apikey: process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!,
      },
      body: JSON.stringify({ name }),
    });

[filipecabaco]

added the same logic to HTTP Broadcast push