swancustomenvironments: Add a 45s timeout on cloning

As ATS clusters do not access to the internet, causing repository clones from Github to fail.
The git command timeout takes about 2 minutes to take action, but after around one minute, the frontend invokation to the backend gets timed out too, but without printing any message informing the user about the reason for it to fail. For this reason, a slightly smaller timeout (of 45s) needs to be explicitly done in the script to lead to an error that outputs a useful feedback in the frontend.

Author: rodrigo-sobral

SwanCustomEnvironments/swancustomenvironments/scripts/makenv.sh

@@ -140,7 +140,7 @@ if [[ "$REPOSITORY" =~ $REPO_GIT_PATTERN ]]; then
     # Otherwise, use the existing one in the SWAN_projects folder
     if [ ! -d "${GIT_REPO_PATH}" ]; then
         _log "Cloning the repository from ${REPOSITORY}..."
-        git clone $REPOSITORY -q "${TMP_REPO_PATH}" 2>&1
+        timeout 45s git clone $REPOSITORY -q "${TMP_REPO_PATH}" 2>&1
         if [ $? -ne 0 ]; then
             _log "ERROR: Failed to clone Git repository" && exit 1
         fi