GRPC received message is set to default when launching external chaincode in 2.2

[ChrisBampis]

I m using HLF v2.2 and external chaincode as a service. After a lot of debugging I have realised that the cc launcher of the peer is limiting the received message to 4 MB. This is the default value set from the @grpc/grpc-js package export const DEFAULT_MAX_RECEIVE_MESSAGE_LENGTH = 4 * 1024 * 1024; . When executing a large query I get the chaincode stream terminated.

2024-04-03 11:51:20.618 UTC [chaincode] HandleGetQueryResult -> DEBU 9ab1e Got keys and values. Sending RESPONSE
2024-04-03 11:51:20.618 UTC [chaincode] HandleTransaction -> DEBU 9ab1f [81060428] Completed GET_QUERY_RESULT. Sending RESPONSE
2024-04-03 11:51:20.850 UTC [chaincode] ProcessStream -> DEBU 9ab20 rpc error: code = ResourceExhausted desc = Received message larger than max (4339799 vs. 4194304)
receive from chaincode support stream failed
github.com/hyperledger/fabric/core/chaincode.(*Handler).ProcessStream
    /go/src/github.com/hyperledger/fabric/core/chaincode/handler.go:395
github.com/hyperledger/fabric/core/chaincode.(*ChaincodeSupport).HandleChaincodeStream
    /go/src/github.com/hyperledger/fabric/core/chaincode/chaincode_support.go:125
github.com/hyperledger/fabric/core/chaincode/extcc.(*ExternalChaincodeRuntime).Stream
    /go/src/github.com/hyperledger/fabric/core/chaincode/extcc/extcc_handler.go:68
github.com/hyperledger/fabric/core/chaincode.(*RuntimeLauncher).Launch.func1
    /go/src/github.com/hyperledger/fabric/core/chaincode/runtime_launcher.go:90
runtime.goexit

2024-04-03 11:51:20.851 UTC [grpc] Infof -> DEBU 9ab24 Channel Connectivity change to SHUTDOWN
2024-04-03 11:51:20.851 UTC [grpc] Infof -> DEBU 9ab25 Subchannel Connectivity change to SHUTDOWN

I have tested the behaviour with IBP peer images and fabric images of v2.2. Has anyone run into this issue before?