test(@angular/cli): configure always-auth for Yarn Classic v1 registry authentication

Configure always-auth in the written .npmrc and .yarnrc test profiles within
createNpmConfigForAuthentication.

By default, Yarn Classic (v1) does not send the Authorization header on GET requests (such as
retrieving manifest metadata via yarn info) unless always-auth is enabled. When ng update uses the
PackageManager abstraction under Yarn Classic v1, this ensures the necessary authorization headers
are sent to secure registry endpoints.

Author: clydin

tests/e2e/tests/update/update-secure-registry.ts

@@ -34,6 +34,6 @@ export default async function () {
     await createNpmConfigForAuthentication(true, true);
 
     const error = await expectToFail(() => exec('yarn', 'ng', 'update', ...extraArgs));
-    assert.match(error.message, /not allowed to access package/);
+    assert.match(error.message, /not allowed to access package|status code 403/);
   }
 }

tests/e2e/utils/registry.ts

@@ -75,10 +75,13 @@ export async function createNpmConfigForAuthentication(
     scopedAuthentication
       ? `
 ${registry}/:_auth="${token}"
+${registry}/:always-auth=true
+always-auth=true
 registry=http:${registry}
 `
       : `
 _auth="${token}"
+always-auth=true
 registry=http:${registry}
 `,
   );
@@ -88,10 +91,13 @@ registry=http:${registry}
     scopedAuthentication
       ? `
 ${registry}/:_auth "${token}"
+${registry}/:always-auth true
+always-auth true
 registry http:${registry}
 `
       : `
 _auth "${token}"
+always-auth true
 registry http:${registry}
 `,
   );