[BUG] Generic error for persistent task on starting replication

[soosinha]

What is the bug?
When start replication API fails due to failure in starting persistent task, the exact reason does not appear in the response. The response has a generic error message Timed out when waiting for persistent task after 1m

How can one reproduce the bug?
Steps to reproduce the behavior:

1. Create an index testindex123 and create an alias testindex for it on the leader cluster.
2. start replication with leader index name as testindex123 and follower index name as testindex
3. This should error out with above generic message.

What is the expected behavior?
The specific error while starting the replication should appear in the response. In the logs, the error is printed as cannot rename index [testindex123] into [testindex] because of conflict with an alias with the same name. This message should be bubbled up and returned in the response.
The simulation is for one scenario. All the scenarios should be listed for failure of starting persistent task and appropriate error message should be returned