[BUG] Search module for VM sizes not working correctly

I am working on a GHA workflow that uses MAPT to create Azure instances like this:

    - name: Create instance
      run: |
        # Create instance
        podman run -d --name windows-create --rm \
          -v ${PWD}:/workspace:z \
          -e ARM_TENANT_ID=${{ secrets.ARM_TENANT_ID }} \
          -e ARM_SUBSCRIPTION_ID=${{ secrets.ARM_SUBSCRIPTION_ID }} \
          -e ARM_CLIENT_ID=${{ secrets.ARM_CLIENT_ID }} \
          -e ARM_CLIENT_SECRET='${{ secrets.ARM_CLIENT_SECRET }}' \
          ${{ env.MAPT_IMAGE }}:${{ env.MAPT_VERSION }} azure \
            windows create \
            --project-name 'windows-desktop' \
            --backed-url 'file:///workspace' \
            --conn-details-output '/workspace' \
            --windows-version '${{ matrix.windows-version }}' \
            --windows-featurepack '${{ matrix.windows-featurepack }}' \
            --nested-virt \
            --cpus 4 \
            --memory 16 \
            --tags project=podman-desktop,source=github,org=${{github.repository_owner}},run=https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }} \
            --spot
        # Check logs 
        podman logs -f windows-create

And I'm experiencing inconsistencies while running it, sometimes it would work as expected and other times it would just break when ran with the exact same parameters, I can't find a pattern. After some discussion with @adrianriobo he came to the conclusion that maybe the search module for VM sizes is not working correctly. Attached you will find a log for an unsuccessful execution of the previously shown step.

create_azure_instance_log.txt

Start with the azure windows create command and reproduce the workflow using the exact parameters shown. Inspect the attached unsuccessful log while tracing the VM-size search behavior. Done means repeated runs with identical parameters select a valid VM size consistently instead of failing intermittently.