Arista AP sends EOF error in the middle of telemetry stream

[JoseIgnacioTamayo]

This happens only with an Arista (Mojo) AP so far:

SubscribeStream(/access-points/access-point[hostname=*]/radios/radio[id=1][operating-frequency=FREQ_2GHZ]/state) <= gRCP Error: <_MultiThreadedRendezvous of RPC that terminated with: status = StatusCode.UNKNOWN details = "EOF" debug_error_string = "UNKNOWN:Error received from peer ipv4:100.77.250.244:8080 {created_time:"2022-11-18T01:00:57.051639987-08:00", grpc_status:2, grpc_message:"EOF"}"

In the telemetry stream started with a gNMI Subscribe, the Target returns a gRPC error that contains a message "EOF". If the intention is to signal EndOfBatch, the gNMI specification tells how to do it (https://github.com/openconfig/reference/blob/master/rpc/gnmi/gnmi-specification.md#3514-the-subscriberesponse-message)

oc_config_validate cannot deal with this gRCP error that is not an error, currently it is interpreted as if the stream was broken.