feat(options): make axe.ping configurable with pingWaitTime

[WilcoFiers]

• Document the existence of pingWaitTime
• Have pingWaitTime: 0 skip the ping step altogether

Closes issue: #3272

[scurker]

Just so I follow:

Setting pingWaitTime to 0 means that only an axe.run is sent? Is this making the assumption that we're re-implementing a ping in the axe extension to first validate that we can communicate with a frame?

My concern lies that if only a single call is made, we don't want to wait 60000ms to timeout if the frame is unable to communicate. We can implement our own ping method in the extension that encompasses both, but just FYI.