Broadcastify Calls upload does not support unique API Key per feed

[TAC-COM-GUY]

sdrtrunk Version
0.6.1 Beta 3

Describe the bug
Uploading fails to a second Broadcastify Calls system unless the API key matches the first system.

To Reproduce
Steps to reproduce the behavior:

1. Need to monitor traffic intended for separate Broadcastify calls systems.
2. Need unique API key assigned for each system by Broadcastify
3. Provision each stream to have separate API key and separate system ID
4. While running, the second streaming feed will fill up the temporary files and they will not be uploaded.
5. Change the API key for the second feed to match the first. Streaming to Calls platform will now work.

Expected behavior
Should be able to have unique API key for each system to allow portability while maintaining good security practices (ie redeploy of receiver at separate location).

Screenshots
N/A

Application Log
There is no logging associated with Broadcastify Calls as noted in a separate feature request

Desktop (optional - complete the following information):

• OS: Ubunutu 24.04.1
• CPU Cores: 4 Cores
• RAM: 8GB

Additional context
N/A