[EPIC] Improve usage for spot-price functionality as a module

[adrianriobo]

Beyond using directly mapt as a provisioning tool, it can be used as module to expose the spot-price logic, being used in that way another existing pieces of code can benefit of the logic.

• Allow find out vm type based on certain parameters (CPU, RAM, Nested Virtualization, arch, GPU acceleration) #281
• Review how to setup credentials to invoke the functions
• Review types/func coding
• Expose func as cli operation?

[adrianriobo]

This is related to #222 you can make use of it to get similar types once you get a type which matches the expectations.

If it does not apply just close as we will use this module instead.

[anjannath]

This is related to #222 you can make use of it to get similar types once you get a type which matches the expectations.

If it does not apply just close as we will use this module instead.

i did not explore this, (difficulity trying out resource manager graph queries) so currently using the Azure SDK to fetch all the VM SKUS and then filter based on its capabilities to find out the desired machine. (https://learn.microsoft.com/en-us/rest/api/compute/resource-skus/list?view=rest-compute-2024-07-01&tabs=Go#lists-all-available-resource-skus)

but this needs the families of VMs that offer nested virtualization, as from the SKU capabilities there's no field which mentions about nested virt support

[adrianriobo]

Closed by #284