Remove enclave type usage in sandbox (#6626)

doc/build_apps/run_app.rst

@@ -45,7 +45,7 @@ For example, deploying the generic JS application:
 
 .. note::
 
-    - ``sandbox.sh`` defaults to using CCF's `virtual` mode, which does not require or make use of SGX. To load debug or release enclaves and make use of SGX, ``--enclave-type`` must be set to the right value, for example: ``sandbox.sh --enclave-type release -p ./libjs.enclave.so.signed``
+    - ``sandbox.sh`` automatically uses the platform which either the local build or install of CCF targeted, i.e. either Virtual or SNP.
     - The ``--verbose`` argument can be used to display all commands issued by operators and members to start the network.
 
 The command output shows the addresses of the CCF nodes where commands may be submitted (ie, via ``curl https://127.0.0.1:8000/...``).

tests/sandbox/sandbox.sh

@@ -20,11 +20,6 @@ if [ ! -f "${VERSION_FILE}" ]; then
     PLATFORM_FILE=PLATFORM
 fi
 platform=$(<"${PLATFORM_FILE}")
-if [ "${platform}" == "sgx" ]; then
-    enclave_type="release"
-else
-    enclave_type="debug"
-fi
 
 extra_args=()
 while [ "$1" != "" ]; do
@@ -119,7 +114,6 @@ export CURL_CLIENT=ON
 export INITIAL_MEMBER_COUNT=1
 exec python "${START_NETWORK_SCRIPT}" \
     --binary-dir "${BINARY_DIR}" \
-    --enclave-type "${enclave_type}" \
     --enclave-platform "${platform}" \
     --constitution "${CONSTITUTION_DIR}"/actions.js \
     --constitution "${CONSTITUTION_DIR}"/validate.js \