FabricIntIngressDropReportTest fails randomly

[Yi-Tseng]

CI job 466 failed because the FabricIntIngressDropReportTest failed. However, when rerunning the job, the test passed. The test also passed on the server when running it manually. I believed that there might be a small chance which causes a hash collision and cause the drop report filter to drop the INT report. Need to do further investigation.

[charlesmcchan]

I also hit the same issue recently. Got around by retesting it.

[ccascone]

We have methods to reset registers to 0 (at least for pipe 0). Should we use that to clean up filters after each test?

[Yi-Tseng]

Yes, I think we can just use the P4Runtime to reset it. I can send a PR to fix this