refactor(ng-dev): properly check if wombot proxy is logged in when checking npm login state

Wombot proxy now supports whoami lookups, so we can now actually check if our token is valid instead of always assuming its not.

Author: josephperrott

ng-dev/release/publish/index.ts

@@ -205,17 +205,6 @@ export class ReleaseTool {
    */
   private async _verifyNpmLoginState(): Promise<boolean> {
     const registry = `NPM at the ${this._config.publishRegistry ?? 'default NPM'} registry`;
-    // TODO(josephperrott): remove wombat specific block once wombot allows `npm whoami` check to
-    // check the status of the local token in the .npmrc file.
-    if (this._config.publishRegistry?.includes('wombat-dressing-room.appspot.com')) {
-      Log.info('Unable to determine NPM login state for wombat proxy, requiring login now.');
-      try {
-        await NpmCommand.startInteractiveLogin(this._config.publishRegistry);
-      } catch {
-        return false;
-      }
-      return true;
-    }
     if (await NpmCommand.checkIsLoggedIn(this._config.publishRegistry)) {
       Log.debug(`Already logged into ${registry}.`);
       return true;