docs: fix broken and malformed documentation links

- examples/science/af3-slurm: correct "htpps://" -> "https://" in the
  Google Cloud Console link.
- community/cos-nvidia-bug-report: remove stray escaped parens around the
  COS documentation URL: ](\(https://...\)) -> ](https://...).
- examples/cae and community/examples/eda: fix the broken relative link to
  the startup-script module README (directory is "startup-script", not
  "startup-scripts"; the eda link also needed one more "../").

Author: manumishra12

community/cos-nvidia-bug-report/README.md

@@ -97,7 +97,7 @@ Before running the script, ensure you have:
 
 2. The GPU driver is installed on the GCE VM instance.
    * Please refer to
-        [COS's official documentation page](\(https://cloud.google.com/container-optimized-os/docs/how-to/run-gpus#install\))
+        [COS's official documentation page](https://cloud.google.com/container-optimized-os/docs/how-to/run-gpus#install)
         for more detail.
    * Sample commands to install the GPU driver and verify the installation:
    * ***NOTE:*** For GKE the driver is already installed. Unless opted for [manual driver installation](https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#create-gpu-pool-auto-drivers)

community/examples/eda/README.md

@@ -226,7 +226,7 @@ Depending on the software you want to use, different installation paths may be r
   ```
 
   where you can follow the installation steps manually. Or using the toolkit's
-  [startup-script](../../modules/scripts/startup-scripts/README.md) module, the process
+  [startup-script](../../../modules/scripts/startup-script/README.md) module, the process
   can be automated.
 
   Once that is completed, the software will persist on the NetApp Volumes share for as long as you

examples/cae/README.md

@@ -222,7 +222,7 @@ Depending on the software you want to use, different installation paths may be r
   ```
 
   where you can follow the installation steps manually. Or using the toolkit's
-  [startup-script](../../modules/scripts/startup-scripts/README.md) module, the process
+  [startup-script](../../modules/scripts/startup-script/README.md) module, the process
   can be automated.
 
   Once that is completed, the software will persist on the NFS Filestore share for as long as you

examples/science/af3-slurm/README.md

@@ -313,7 +313,7 @@ This solution uses various GCS buckets to store required persistent information:
    This bucket is expected to contain a copy of the AlphaFold 3 weights as provided by the process
    described in section [AlphaFold 3 Model Weights](#alphafold-3-model-weights).
 
-   You can use [Google Cloud Console](htpps://console.cloud.google.com) to upload the
+   You can use [Google Cloud Console](https://console.cloud.google.com) to upload the
    uncompressed `af3.bin` weights file. Alternatively, you can execute on a shell where you have the weights and gcloud commands installed:
 
    ```bash