[BUG]The Extarctor Pipeline have variables of github in azure devops pipeline

[h-karthik12]

Release version

APIOps Toolkit for Azure APIM v6.0.0-alpha.1.0.4

Describe the bug

          Write-Information "Downloading release..."
            $uri = "https://github.com/Azure/apiops/releases/download/${{ env.apiops_release_version }}/$releaseFileName"
            $downloadFilePath = Join-Path "${{ runner.temp }}" $releaseFileName
            Invoke-WebRequest -Uri "$uri" -OutFile "$downloadFilePath"
            
            Write-Information "Extracting release..."
            $executableFolderPath = Join-Path "${{ runner.temp }}" "extractor"
            Expand-Archive -Path "$downloadFilePath" -DestinationPath "$executableFolderPath"
            $executableFilePath = Join-Path "$executableFolderPath" $executableFileName
            
            Write-Information "Setting file permissions..."
            if ("${{ runner.os }}" -like "*linux*")

Expected behavior

should have azure devops parameters

Actual behavior

have git hub parameters

Reproduction Steps

add it to the pipleine and validate will thrown an validation error

[github-actions]

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

[waelkdouh]

Thanks for raising this to our attention. Please avoid using the alpha version for now. Please utilize version https://github.com/Azure/apiops/releases/tag/v5.1.4 for now. We have some outstanding issues with the alpha version that we are working on fixing.

[waelkdouh]

Seems like these issues have been fixed. Please check now.