[Reporting] Handle error scenarios for deleted user and deleted saved object

[tsullivan]

In the Reporting plugin, we have error codes that are assigned during report job runs in case the job fails. These codes are used to create meaningful error messages to users when the view the error details in the Reporting UI (Stack Management > Alerts & Insights > Reporting).

Error codes for Reporting are mapped in https://github.com/elastic/kibana/blob/ae18346f0e0a0cc1e5ef18aaa9c27d34010279bb/x-pack/plugins/reporting/common/errors/map_to_reporting_error.ts#L45

Update the set of known errors and add codes for the following:

• Data View saved object is deleted: During CSV export, when the report job runs it tries to load the data view saved object. If that data view saved object is not found, we need to provide a specific error of this scenario.
• User authentication fails: During CSV export, if the cached user authentication details can't be used to read data from Elasticsearch, the report job will fail. We need to provide a specific error of this scenario.

Other:

• Report job document is missing: Before any type of report job runs, Task Manager fires a task to the Reporting plugin, which reacts by attempting to load the report job document from the Reporting plugin's data stream. If this fails, nothing further can proceed, and in this case we can't write a specific error code anywhere because the report job document doesn't exist. We can reduce the possibility of this occurring by updating the Delete Report API to unschedule the task from task manager when a report document is deleted. This work is tracked by https://github.com/elastic/kibana/issues/191551

[elasticmachine]

Pinging @elastic/appex-sharedux (Team:SharedUX)