Using a azPSVersion other than latest adds 2-6 minutes to the job

[jtomkiew-mng]

In our use case we would prefer to use specific Az module versions, as opposed to whatever is available on the agent. Relying on specific agent version is not ideal either, as those are not granular enough to "care" about Az modules.

Using azPSVersion parameter works, but introduces a rather long delay (2+ minutes), as modules of specific version need to be installed, examples:

Fig. 1: Job execution time depending on runner agent and azPSVersion value

Fig. 2: Same as above, executed 5 minutes later (notice the rather large difference).

I understand that this is mostly due to the large number of Az modules and relying on PowerShell Gallery (which is known to be slow at times).

Based on that we can define 2 pain points:

1. having to install all 90+ Az modules at a time
   => possible action: limiting installation to specific modules, based on action input (this would be for advanced users that are fully aware of what modules they depend on)
2. relying on public PowerShell Gallery that has performance issues at times
   => possible action: allowing to cache and reuse module files (something like this)

Do let me know if those 2 action points above sound ridiculous or not.