Schedule the TTS engine call as a job if the parser function is being called from another job ($wgCommandLineMode = true) or if expensive parser function limit was reached. In T315483 we decided not to render the button if the expensive parser function limit was hit but that should not be a problem now because we run the expensive bit as a job if that happens
Follow up to T318086: Create phonos Jobs to handle mass file generation
Acceptance Criteria
- The button should always be rendered and the url to the file should always be present. If the audio file is not ready, an error message should be displayed on click.
- If the phonos parser function is called from a cli command (Ex. another job) and the file does not exist or if expensive parser function limit was reached, it should fire up the phonosIPAFilePersist job instead of generating the file synchronously