Azure DevOps Artifacts support for registry-url

[tylerjwatson]

Description: actions/setup-node does not support Azure DevOps Artifacts even though DevOps is also a Microsoft product. This is because actions/setup-node configures a temporary .npmrc file with an _authToken syntax, but AzureDevops requires npm's :username, ":_password", and ":email" syntax.

This patch adds support for Azure DevOps, and other registries by adding a username action input parameter. When this is input is set, the .npmrc file will be written with a :username, :_password and :email instead of an :_authToken.

Fetching private scoped packages from Azure DevOps Artifacts is now supported and working with this patch.

Related issue: N/A

Check list:

• [ ] Mark if documentation changes are required.
• [ ] Mark if tests were added or updated to cover the changes.

[erdenerrallas19]

?

[andyleejordan]

Omg, this needs to be merged. I just spent a day and half hitting my head against my desk unable to get my GitHub Workflows to use my ADO feed (even though I was able to configure Dependabot, on GitHub just fine) only to finally realize the ADO feed requires username/password, not an auth token. And that's not supported (yet). Can't just put it in my .npmrc because then local builds break.

This has been open a year...@dmitry-shibanov can you please review and release this addition? Thank you!

[andyfisher100]

This is a must have for this action in my opinion. Until Github Packages has more investment thrown behind it to add support for more packages types that Azure DevOps has, we will be confined to using Azure DevOps Overall

Can this please be worked on and merged? @dmitry-shibanov it seems this needs a review as suggested by @andyleejordan?

[enyil]

I can see other EMU customers getting this issue. Any updates on this?

[andyleejordan]

This really needs to get in.