Log callbacks for FFprobe includes the executionId of a previous async FFmpeg execution

[tanersener]

Current Behaviour
When the same thread calls Config.ffmpegExecute() first and FFprobe.execute() later, log callbacks received for FFprobe includes the executionId of the ffmpeg execution.

Expected Behaviour
FFprobe does not support async operations. So, log callbacks for FFprobe should always have executionId = 0.

Environment
This issue originates from MobileFFmpeg v4.4 and v4.4.LTS, affects all platforms including react-native and flutter plugins based on MobileFFmpeg.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[tanersener]

Fixed in v4.4 and v4.4.LTS.