terraform fail to destroy maas_instance when disk erase set to default in MAAS

[noama-nv]

PSB expected status after release is the machine to be ready seems like any other status considered as bad
please add this stage as optional in transitioning from deployed to Ready so that the delete timeout is really effective

maas_instance.controllers[0]: Destroying... [id=b4qqxb]
maas_instance.workers[0]: Destroying... [id=6bwhkd]
maas_instance.workers[1]: Destroying... [id=4pdmwt]
maas_instance.workers[1]: Still destroying... [id=4pdmwt, 10s elapsed]
maas_instance.workers[0]: Still destroying... [id=6bwhkd, 10s elapsed]
maas_instance.controllers[0]: Still destroying... [id=b4qqxb, 10s elapsed]
maas_instance.controllers[0]: Destruction complete after 11s
maas_instance.workers[0]: Still destroying... [id=6bwhkd, 20s elapsed]
maas_instance.workers[1]: Still destroying... [id=4pdmwt, 20s elapsed]
maas_instance.workers[0]: Still destroying... [id=6bwhkd, 30s elapsed]
maas_instance.workers[1]: Still destroying... [id=4pdmwt, 30s elapsed]
maas_instance.workers[1]: Still destroying... [id=4pdmwt, 40s elapsed]
maas_instance.workers[0]: Still destroying... [id=6bwhkd, 40s elapsed]
maas_instance.workers[1]: Still destroying... [id=4pdmwt, 50s elapsed]
maas_instance.workers[0]: Still destroying... [id=6bwhkd, 50s elapsed]
╷
│ Error: unexpected state 'Disk erasing', wanted target 'Ready'. last error: %!s(<nil>)
│ 
│ 
╵
╷
│ Error: unexpected state 'Disk erasing', wanted target 'Ready'. last error: %!s(<nil>)
│ 
│ 
╵
Releasing state lock. This may take a few moments...