Firmware, Testing with Out DFPlayer GPAD_API should not hang.

[ForrestErickson]

Describe the bug
A clear and concise description of what the bug is.
Short Summary of the expected behavior:
When testing the GPAD_API on incomplete hardware such as an ESP32 Dev Kit I expect the code to run as best it can and report missing hardware.

Short Summary of the buggy behavior:
On an ESP32 Dev Kit the firmware appars to hang somewhere after the Serial.println("DFPlayer Mini detected!")
and the call to displayDFPlayerStats();

Additionally the DUT should never have printed "DFPlayer Mini detected!"
This test is returning false result.

To Reproduce
Steps to reproduce the behavior:

1. Test with an ESP32 Dev Kit1
2. Load code from older than 0.45.
3. Observe the serial monitor

Expected behavior
A clear and concise description of what you expected to happen.
We want the code never to hang even if hardware is missing.

[ForrestErickson]

Notes on the DFPlayer testing in the FactoryTest_wMenu

Test on DUT with Mini MP3 Player

Enter command: 4
initDFPlayer() called at: 5993
Initializing DFPlayer (UART2)...
InitDFPlayer, dfPlayer.available(): 0

Test on DUT with OUT a Player

Enter command: 4
initDFPlayer() called at: 5355
Initializing DFPlayer (UART2)...
InitDFPlayer, dfPlayer.available(): 0
  DFPlayer not detected. Check wiring & power.
 DFPlayer initializing Failed (DFPlayer not detected).
dfPlayer.available(): 0

Here is the code which reports the status of the Mini MP3 player