LambdaTest tunnel has now a different tunnel ready message

[ArpitLT]

There is an issue with LambdaTest tunnel which gets timed out in polling mode through Jenkins due to different tunnel ready message with geb-lambdatest plugin when tunnel is started in polling mode instead of websocket mode. We have modified the tunnel ready message. This will fix the lambdatest tunnel getting started with Jenkins . We need your help @erdi in committing it.
Pull Request

final String tunnelReadyMessage = 'Tunnel claim successful'
to
final String tunnelReadyMessage = 'Secure connection established, you may start your tests now'

[ArpitLT]

Hi @erdi ,
Hope you're all well and safe in this Covid-19 outbreak. The LambdaTest tunnel can work in two modes: websocket and polling mode. However, in both modes, tunnelReady messages are different which caused problems when the tunnel is started in polling mode. This makes the plugin timeout as it doesn't find the exact text when tunnel starts in polling mode (with nows argument).

https://github.com/geb/geb/blob/master/integration/geb-gradle/src/main/groovy/geb/gradle/lambdatest/LambdaTestTunnel.groovy

To resolve this issue, we'd like you to update tunnelReadyMessage for which we've raised a pull request as well:

final String tunnelReadyMessage = 'Tunnel claim successful'
to
final String tunnelReadyMessage = 'Secure connection established, you may start your tests now'