--no-wait parameter and wait command have a bug

> ### `az feedback` auto-generates most of the information requested below, as of CLI version 2.0.62

**Describe the bug**

I discovered a bug recently. `wait` command calls GET method of the resource. It gets a "Resource not found" error if the resource has not been created. Here, "created" means it can be GET. It does not mean the provisioning is finished. It should query operation status, not resource status. Operation query address is returned in Azure-AsyncOperation header of a long running operation.

**Solution 1**
`--wait` returns until the resource is created and can be found with GET.

**Solution 2**
`wait` queries operation status instead of resource status.

**To Reproduce**

**Expected behavior**

**Environment summary**

**Additional context**