Fix unexpected script_path behaviour

When one calls the build.sh scripts with bash instead of the shebang $script_path contains the filepath, not the parent dir:

# cd /path
# grep -A2 script_path= build.sh
script_path=$(readlink -f "${0%/*}")
echo "$script_path"
exit 0
# ./build.sh
/path
# bash build.sh
/path/build.sh

This commit fixes that:

# grep -A2 script_path= build.sh
script_path="$( cd -P "$( dirname "$(readlink -f "$0")" )" && pwd )"
echo "$script_path"
exit 0
# ./build.sh
/path
# bash build.sh
/path

configs/baseline/build.sh

@@ -10,7 +10,7 @@ arch=$(uname -m)
 work_dir=work
 out_dir=out
 
-script_path=$(readlink -f "${0%/*}")
+script_path="$( cd -P "$( dirname "$(readlink -f "$0")" )" && pwd )"
 
 umask 0022