Adjusted authenticator script to allow running publishing in dev ops.

[azaslonov]

Problem: We have recently deprecated direct MAPI access in the APIM service, so the portal now uses ARM APIs for content management and Data APIs for fetching the data (like APIs, operations, products, etc.). The customers sometimes need to run certain operations like publishing in dev ops pipeline (e.g., GitHub Actions) which needs a way to authenticate against ARM APIs. For that the pipeline has to use client_credentials flow to acquire the token. Hence, the script needs to take this flow into account.

Example of GitHub Actions pipeline YAML:

name: Portal-Publishing-Pipeline

on:
  pull_request:
    branches:
      - master

jobs:
  publish:
    runs-on: ubuntu-latest
    env:
      AZURE_TENANT_ID: ${{ secrets.AZURE_TENANT_ID }}
      AZURE_CLIENT_ID: ${{ secrets.AZURE_CLIENT_ID }}
      AZURE_CLIENT_SECRET: ${{ secrets.AZURE_CLIENT_SECRET }}
    steps:
      - name: Checkout code
        uses: actions/checkout@v5

      - name: Set up Node.js
        uses: actions/setup-node@v5
        with:
          node-version: '20.x'

      - name: Install dependencies
        run: npm install

      - name: Run publishing
        run: npm run publish

Respective documentation will be published soon.