Add authorization header when unregistered user starts a meeting via invite link

summary

rooms/{room_id}/start_invited endpoint is going to be a protected resource

In case the user is registered, frontend appends Authorization Bearer {acces_token}

For an unregistered user frontend should append Authorization InviteCode {invite_code}

Similarly as it is done for GET /room/{room_id}/event

acceptance criteria

• If user starts a meeting via invite link:
  • If user is registered the header of the POST rooms/{room_id}/start_invited shall contain Authorization Bearer {acces_token}
  • If user is not registered the header of the POST rooms/{room_id}/start_invited shall contain Authorization InviteCode {invite_code} *