Feature reeust: Advanced (custom) task configuration

[stqp]

https://docs.lagoon.sh/using-lagoon-advanced/custom-tasks/

1. It would be convenient for japanese clients if custom tasks could be configurable via a yml file (e.g. .lagoon.yml) similar to pre post rollout tasks.
2. For clients not using Drupal, it would be less confusing if the default drush command tasks could be deletable.

[shreddedbacon]

We don't plan to support the creation of tasks inside of the .lagoon.yml file, it is difficult to manage them over all. What happens if one branch has a task that another branch doesn't have? Who can manage the execution of the task based on permission? How is it triggered? These are all too difficult to manage from this file.

We are working on making advanced tasks (custom tasks) easier to use and consume though, work is ongoing to do this.

As for the default drupal tasks you mentioned, these will be removed in a future version of Lagoon, once we finalise the new advanced tasks implementation