Convert Publisher yaml to classic pipeline

### Release version

ApiOps v6.0.1.7

### Question Details

Subject: Issue with JWT Token Handling in APIOps Publisher Pipeline

Description: As my Organization has restrictions in creating Yaml pipelines at release level. I am trying to create a classic release pipeline for publisher pipeline .We are encountering an issue where the APIOps Publisher pipeline does not correctly handle the JWT token. Even after hardcoding a valid JWT token, the execution fails with the following error:
JWT is not well formed, there are no dots (.).
The token needs to be in JWS or JWE Compact Serialization Format.

Troubleshooting Steps Taken:

Verified that the JWT token is correctly formatted (three parts separated by dots).
Printed the token before execution to confirm correct passing.
Removed unnecessary quotes while passing the token in the command.

### Expected behavior

The APIOps Publisher should accept the valid JWT token without throwing a format error and publish the artifacts to APIM

### Actual behavior

The tool incorrectly reports that the token is not well-formed, preventing execution.

### Reproduction Steps

Download and extract the latest APIOps Publisher tool.
Define a valid JWT token with three parts (header.payload.signature).
Execute the following command:& "$publisherPath" --config "$artifactPath/configuration.extractor.yaml" --token $jwttesttoken
The process fails, stating that the JWT token is not well-formed.

Inizia riproducendo il comando usando la pipeline di release classica, publisherPath, artifactPath/configuration.extractor.yaml e l’argomento jwttesttoken descritti nell’issue. L’attività è completata quando un JWT valido composto da tre parti raggiunge APIOps Publisher senza l’errore di formato e gli artefatti vengono pubblicati in APIM.

Scritto dal modello di indicizzazione a partire dal testo della issue.