Spot feature is failing on azure due to capacity

Investigate the issue occurring randomly, this should not occur due to picked eviction rate, we should review the algo

{"level":"error","msg":"failed to run update: exit status 255\ncode: 255\nstdout: Updating (stackCreateWindowsDesktop-windows-desktop-11-23h2-ent-e2e-microshift):\n\n +  pulumi:pulumi:Stack windows-desktop-11-23h2-ent-e2e-microshift-stackCreateWindowsDesktop-windows-desktop-11-23h2-ent-e2e-microshift creating (0s) \n@ updating......\n +  random:index:RandomPassword awd-pswd-adminuser creating (0s) \n +  random:index:RandomPassword awd-pswd-user creating (0s) \n@ updating....\n +  random:index:RandomPassword awd-pswd-adminuser created (0.90s) \n@ updating....\n +  random:index:RandomPassword awd-pswd-user created (1s) \n@ updating......\n +  tls:index:PrivateKey awd-privatekey-user creating (0s) \n@ updating......\n +  azure-native:resources:ResourceGroup awd-rg creating (0s) \n +  tls:index:PrivateKey awd-privatekey-user created (2s) \n@ updating......\n +  azure-native:resources:ResourceGroup awd-rg created (3s) \n@ updating....\n +  azure-native:storage:StorageAccount awd-sa creating (0s) \n +  azure-native:network:PublicIPAddress awd-pip creating (0s) \n +  azure-native:network:VirtualNetwork awd-vn creating (0s) \n@ updating..........\n +  azure-native:network:PublicIPAddress awd-pip created (7s) \n@ updating......\n +  azure-native:network:VirtualNetwork awd-vn created (9s) \n@ updating....\n +  azure-native:network:Subnet awd-sn creating (0s) \n@ updating.........\n +  azure-native:network:Subnet awd-sn created (5s) \n@ updating....\n +  azure-native:network:NetworkInterface awd-ni creating (0s) \n@ updating........\n +  azure-native:network:NetworkInterface awd-ni created (5s) \n@ updating....\n +  azure-native:storage:StorageAccount awd-sa created (23s) \n@ updating....\n +  azure-native:compute:VirtualMachine awd-vm creating (0s) \n +  azure-native:storage:BlobContainer awd-co creating (0s) \n@ updating.......\n +  azure-native:storage:BlobContainer awd-co created (3s) \n@ updating....\n +  azure-native:storage:Blob awd-bl creating (0s) \n@ updating......\n +  azure-native:storage:Blob awd-bl created (2s) \n@ updating.....\n +  azure-native:compute:VirtualMachine awd-vm creating (10s) error: autorest/azure: Service returned an error. Status=\u003cnil\u003e Code=\"OperationNotAllowed\" Message=\"Unable to perform operation 'Create VM' since the provided max price '0.0796 USD' is lower than the current spot price '0.105072 USD' for Azure Spot VM size 'Standard_D8s_v5'. For more information, see [http://aka.ms/AzureSpot/errormessages.\](http://aka.ms/AzureSpot/errormessages./)"\n +  azure-native:compute:VirtualMachine awd-vm **creating failed** error: autorest/azure: Service returned an error. Status=\u003cnil\u003e Code=\"OperationNotAllowed\" Message=\"Unable to perform operation 'Create VM' since the provided max price '0.0796 USD' is lower than the current spot price '0.105072 USD' for Azure Spot VM size 'Standard_D8s_v5'. For more information, see [http://aka.ms/AzureSpot/errormessages.\](http://aka.ms/AzureSpot/errormessages./)"\n@ updating.....\n +  pulumi:pulumi:Stack windows-desktop-11-23h2-ent-e2e-microshift-stackCreateWindowsDesktop-windows-desktop-11-23h2-ent-e2e-microshift creating (52s) error: update failed\n +  pulumi:pulumi:Stack windows-desktop-11-23h2-ent-e2e-microshift-stackCreateWindowsDesktop-windows-desktop-11-23h2-ent-e2e-microshift **creating failed (51s)** 1 error\nDiagnostics:\n  azure-native:compute:VirtualMachine (awd-vm):\n    error: autorest/azure: Service returned an error. Status=\u003cnil\u003e Code=\"OperationNotAllowed\" Message=\"Unable to perform operation 'Create VM' since the provided max price '0.0796 USD' is lower than the current spot price '0.105072 USD' for Azure Spot VM size 'Standard_D8s_v5'. For more information, see [http://aka.ms/AzureSpot/errormessages.\](http://aka.ms/AzureSpot/errormessages./)"\n\n  pulumi:pulumi:Stack (windows-desktop-11-23h2-ent-e2e-microshift-stackCreateWindowsDesktop-windows-desktop-11-23h2-ent-e2e-microshift):\n    error: update failed\n\nOutputs:\n    -awdAdminUserPassword: [secret]\n    -awdAdminUsername    : \"rhqpadmin\"\n    -awdHost             : \"23.102.25.229\"\n    -awdUserPassword     : [secret]\n    -awdUserPrivatekey   : [secret]\n    -awdUsername         : \"rhqp\"\n\nResources:\n    + 12 created\n\nDuration: 53s\n\n\nstderr: \n","time":"2024-07-01T07:13:50Z"}

No files or tests are named. Start by locating the Azure Spot VM provisioning path that produces the logged max-price error, then trace how the eviction rate selects that price. Done means the cause of the intermittent failure is identified and the expected behavior for this case is defined and verified.