fix: prevent stop recording for transfers [CHI-3598]

[gpaoloni]

Description

This PR

• Prevents "stop recording" upon participant leave event IF the participant left the conference because of a transfer.
  • Should fix the bug linked below - "should" because we are not certain of the root cause, but this seems like the most logical explanation.
• Small refactor in the code: split function used in loop for readability, prefer early return over nested if statements.

Checklist

• CHI-3598
• New tests added
• Feature flags added
• Strings are localized
• Tested for chat contacts
• Tested for call contacts

Verification steps

AFTER YOU MERGE

1. Cut a release tag using the Github workflow. Wait for it to complete and notify in the #aselo-deploys Slack channel.
2. Comment on the ticket with the release tag version AND any additional instructions required to configure an environment to test the changes.
3. Only then move the ticket into the QA column in JIRA

You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P

[stephenhand]

LGTM - one question, you said you think it will fix it but can't be sure - can we not deterministically test this? If it's any cold transfer causing the issue we should be able to confirm the fix with a 'broken before, fixed after' QA test?

[stephenhand]

Suggested change

	`No participants identified as Aselo agents still in conference ${conferenceSid}, candidate to stop recordings`,
	`No participants identified as Aselo agents still in conference ${conferenceSid}, will stop recordings if this is not a transfer`,

[stephenhand]

Also possibly more of a debug log?