Tags for resource get deleted on second azd up execution which blocks Azure Functions deploy from working

[nzthiago]

• Make sure you've installed the latest version using instructions in the wiki

Output from azd version
azd version 1.10.1 (commit 31409a3)

Describe the bug
Running azd up on a project that has a Function App (Flex Consumption) works the first time but shows the following on subsequent calls:
ERROR: error executing step command 'deploy --all': getting target resource: resource not found: unable to find a resource tagged with 'azd-service-name: processor'. Ensure the service resource is correctly tagged in your infrastructure configuration, and rerun provision

So, after running azd up the first time the app has the tags and deploys correctly:

But after attempting azd up the second time, it fails at the deploy stage because the tags are not there:

To Reproduce
This shows up from time to time. I have just reproduced this with the E2E DURABLE-FUNC-ORDER-PROCESSING sample for Azure Functions Flex Consumption when reviewing this PR so you can use that PR (or the sample from brain if the PR is already merged by the time of reviewing this).

Get the code of the sample down, run azd up, test the app as per readme, then make a small code change and run azd up again.

Expected behavior
Repeated azd up should correctly re-deploy the app.

[weikanglim]

I can see the resource is tagged correctly in the Bicep file. Will need to investigate further.

[nzthiago]

@weikanglim - I have just run into this one again, this time with the https://github.com/Azure-Samples/azure-functions-java-flex-consumption-azd sample. I had run just earlier that sample with SKIP_VNET set to true. Then I did an 'azd down' and deleted the .azure folder. Then tried azd up again but this time without setting SKIP_VNET. Got this:

Then I ran azd up again and this time it publishes fine:

It does seem like there's something strange with the tag search.