[BUG] ICE full start out as CONTROLLED mode

When I set an ice-lite offer to the rest endpoint, Janus is sending out STUN binding requests with CONTROLLED role.

However RFC says the full agent must take controlling role.
RFC referrence

Code pointer: janus-gateway/src/ice.c at master · meetecho/janus-gateway · GitHub
You can see in the log screenshot that the Remote offer is ICE-Lite. and janus being ICE Full, it should be CONTROLLING as per RFC.

I don’t think we have any check on whether the peer is ICE lite or not, since we basically assumed that would never happen. We only have checks for when Janus itself is ICE lite. That’s an interesting use case, but it means we’ll also have to check what happens when both the peer and Janus are ICE lite (which means a PC would never be established).