Disable fuzz coverage test on Bazel CI

[meteorcloudy]

#16542 has been keep Envoy red on Bazel CI for a long time, it doesn't make sense to keep a failing test if it's not going to be fixed.

[repokitteh-read-only]

Hi @meteorcloudy, welcome and thank you for your contribution.

We will try to review your Pull Request as quickly as possible.

In the meantime, please take a look at the contribution guidelines if you have not done so already.

🐱

Caused by: #16940 was opened by meteorcloudy.

see: more, trace.

[zuercher]

@antoniovicente assign you because you seem to have some background based on the referenced issue.

[zuercher]

@meteorcloudy it might be worth discussing the path forward with @antoniovicente first, but if we're going to proceed with this PR, we'll need DCO signoff (see https://github.com/envoyproxy/envoy/blob/main/CONTRIBUTING.md#dco-sign-your-work)

[antoniovicente]

I really don't have context here. This coverage mode was introduced in #14179

I think you should reach out to @lizan, @asraa and @phlax .

Disabling for now SGTM.

[antoniovicente]

I think it is fine to disable this in order to get the bazel CI back to a green state.

[asraa]

That sounds good, as an aside I think the problem may be related to some libc++ flag configuration?