Improve dispatch error management in scheduler

[rsmontero]

Description When a VM cannot be deployed in a host (one.vm.deploy API call) the scheduler tries the next suitable host. When the failure is related to a host condition (e.g. host has been disabled, host capacity exceeded...) this approach can recover the error.

However, some errors only depends on a misconfiguration of the VM (e.g. wrong TM configuration, quotas exceeded,...) In this case the VM should not be deployed in other host as it is going to fail.

This issue is for the scheduler to detect this situation and give up on a giving VM

Use case Improve scheduler performance, reduce oned load on error conditions.

Interface Changes Return code of one.vm.deploy should signal this VM related errors probably with a dedicated error code

Additional Context NaN

Progress Status

• [ ] Branch created
• [ ] Code committed to development branch
• [ ] Testing - QA
• [ ] Documentation
• [ ] Release notes - resolved issues, compatibility, known issues
• [ ] Code committed to upstream release/hotfix branches
• [ ] Documentation committed to upstream release/hotfix branches