Set status to none when recording not found

[vitormattos]

When is short the interval between start and stop request, isn't possible to store the stop request because the start didn't finished as well. Because this was changed error status "recording failed" to stauts equal to none (no recording).

🏁 Checklist

• ⛑️ Tests (unit and/or integration) are included
• 📘 API documentation in docs/ has been updated or is not required
• 📗 User documentation in https://github.com/nextcloud/documentation/tree/master/user_manual/talk has been updated or is not required
• 🔖 Capability is added or not needed

[nickvergessen]

Fine by me, the question is whether that is good enough for the recording server or whether it will finish to start and still record afterwards, but @danxuliu might know better.

[danxuliu]

If the recording was not found the status must be changed to failed. Otherwise the following scenario would not be seen as a failure:

• Start a recording
• Kill the recording server
• Start the recording server again
• Stop the recording (which will trigger a recording not found, as the new recording server instance knows nothing about the recording)

Moreover, in the described scenario of stopping the recording while it is starting and has not fully started yet the failure notification comes from the recording server, it is not related to the API. Therefore closing in favour of #9124.