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 los pasos de reproducción contra la release v6.0.1.4, comenzando con la APIOPs extractor pipeline y su paso «Create artifacts pull request». Compara la customer-grpc apiInformation.json generada con las operaciones de la API gRPC desplegada; el trabajo estará terminado cuando el pull request incluya todas las operaciones del customer profile service proto.

Escrito por el modelo de indexación a partir del texto del issue.