Improve diagnosing of pointer corruption issue

Add an optional parameter to `availableToRead|Write` methods
to inform the client that the state of FMQ pointers seems
to be corrupted. Also, print invalid values in the log message
to assist further investigation.

Bug: 338974476
Test: m
Change-Id: Iec374db654de6888cac644e5cb93f5edb11d9e6f