APIOPs extractor Pipeline not extracting operations of gRPC API in the Pull request.

### Release version

v6.0.1.4

### Describe the bug

APIOPs extractor Pipeline is not extracting operations of gRPC API in the Pull request.. Followed below steps:
1)Created gRPC API in APIM with customer profile service proto file .
2) gRPC API is deployed with multiple operations.
3) While using APIOPs extractor Pipeline, it is not extracting operations of gRPC API in the Pull request.
In the PR, apis folder with gRPC api "customer-grpc" is extracted with only apiInformation.json but operations are not found.
Attached document with screenshots.

### Expected behavior

APIOPs extractor Pipeline should extract all operations of gRPC API in the Pull request.

### Actual behavior

APIOPs extractor Pipeline is not extracting operations of gRPC API in the Pull request.

### Reproduction Steps

1) Create a gRPC API in APIM with customer profile service proto file.
2) gRPC API should be created with multiple operations.
3) Execute the run extractor pipeline of APIOPS.
4) The "Create artifacts pull request" - "Create pull request" step of the extractor pipeline would create a PR.
5) The PR will not have operations data of the gRPC API.

Usa i passaggi per la riproduzione con la release v6.0.1.4, iniziando dalla APIOPs extractor pipeline e dal relativo passaggio «Create artifacts pull request». Confronta la customer-grpc apiInformation.json generata con le operazioni dell’API gRPC distribuita; il lavoro è completato quando il pull request include tutte le operazioni del customer profile service proto.

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