ci: explain why "nolock" mountOption is needed for nfs
ci: explain why "nolock" mountOption is needed for nfs

"nolock" mountOptions has been added to prevent the following error in ci:
Output: mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.

Signed-off-by: Rakshith R <2c7b05ed1488c7110901626c2c56645675e22767@redhat.com>

rook/rook,rook/rook,rook/rook,rook/rook,rook/rook