Auto Extension Resolution logging improvement

[hashlash]

Can we improve the log for notifying users that the k6 process will do the Auto Extension Resolution?

INFO[0000] Automatic extension resolution is enabled. The current k6 binary doesn't satisfy all dependencies, it's required to provision a custom binary.  deps=k6/x/faker

With the k6 process taking some time to build the new binary, the user might misinterpret it as something going wrong. Especially with the "it's required to provision a custom binary" part, which might sound like an instruction for the user to build the binary themself.

Proposal

Here are some things that I could think of to improve it:

• Adding something like Building a new custom binary... to the log (or using debug level log)
• Rephrase the "it's required to provision a custom binary" part
• Adding progress like the one in the cloud command.