EFS RP restore test sometimes fails

[HLebedynets]

Sometimes EFS RP restore test fails with this error:

Mount of AWS EFS 'fs-0b456b6c63f63a76c' failed. Details: Failed to mount 'fs-0b456b6c63f63a76c' device due to error: Failed to mount EFS 'fs-0b456b6c63f63a76c at '/media/elastio/fs-0b456b6c63f63a76c'.

Caused by:
    Command finished abnormally: command: 'mount -t efs -o tls fs-0b456b6c63f63a76c:/ /media/elastio/fs-0b456b6c63f63a76c -o fsc -o ro', exit code: 'Some(1)', signal: 'None', stderr: 'Failed to resolve "fs-0b456b6c63f63a76c.efs.us-east-1.amazonaws.com" - check that your file system ID is correct, and ensure that the VPC has an EFS mount target for this file system ID.
    See https://docs.aws.amazon.com/console/efs/mount-dns-name for more detail.
    Attempting to lookup mount target ip address using botocore. Failed to import necessary dependency botocore, please install botocore first.
    '

It happens when restored EFS mount targets are not created yet, but scan has started.

Possible solution is adding a function for checking if mount targets are created and running it before elastio scan.