'azd down' does not remove deployment state if resources are already gone

[irinasmoke]

Output from azd version
Run azd version and copy and paste the output here: azd version 1.21.3

Describe the bug
When running azd down, if resources have previously been manually deleted, the deployment state is not removed. This leads to subsequent azd provision calls not working properly.

To Reproduce

1. azd up a project
2. Manually delete resource group
3. Run azd down
4. Run azd up
5. Deployment fails because provisioning fails

Expected behavior
azd down should remove deployment state, giving the user a clear path to re-provision, even if resources have already been removed by other means.

Additional context
Actually, the ideal experience would be to have azd provision be able to detect that resources have been manually deleted and be able to re-provision anyway without users needing to know about the --no-state flag, but I have been told this is not so straightforward, so this is my next best proposed solution - at least make azd down behave as expected in this scenario.

[weikanglim]

the ideal experience would be to have azd provision be able to detect that resources have been manually deleted and be able to re-provision anyway without users needing to know about the --no-state flag,

I do very much prefer this behavior of azd checking if resource groups have been delted before proceeding. Proposed a change in #6281 based on this.

[kristenwomack]

Does #6281 also fix and close this issue?