[pulsar-storm] add more metrics to troubleshoot spout throughput

[rdhabalia]

Motivation

Many time user sees lower throughput in pulsar-spout even though standalone consumer can consume such msgRate easily. It would be hard to debug user's topology without enough information so, adding two metrics which can impact spout throughput.

• number of message filed: spout sleeps when it sees failed message so, it's important to have visibility of that count
• number of times spout-thread not found the message in queue: spout topology internally sleeps if it doesn't see any emitted tuple in collector after triggering nextTuple() api.

This metrics gives more visibility about consumer throughput.

[merlimat]

👍

[merlimat]

run integration tests
run java8 tests

[rdhabalia]

rerun java8 tests

[jiazhai]

+1