psu-ng: Continue reading after readFail

Update the PMBus::read() function to allow for not creating journal
trace and elog, but default to continuing to trace and elog, the
previous behavior.

If we reach the limit of read failures that results in a communication
error log, continue to read, but stop logging failures.

If communication restores, we may be able to detect what caused the read
failure, or otherwise detect or clear new faults.

Change-Id: If59b86211ab54c31248ede78f8f117b607298923
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
diff --git a/phosphor-power-supply/test/mock.hpp b/phosphor-power-supply/test/mock.hpp
index 25f48c1..cf4d3ae 100644
--- a/phosphor-power-supply/test/mock.hpp
+++ b/phosphor-power-supply/test/mock.hpp
@@ -19,7 +19,8 @@
   public:
     virtual ~MockedPMBus() = default;
 
-    MOCK_METHOD(uint64_t, read, (const std::string& name, Type type),
+    MOCK_METHOD(uint64_t, read,
+                (const std::string& name, Type type, bool errTrace),
                 (override));
     MOCK_METHOD(std::string, readString, (const std::string& name, Type type),
                 (override));