docs: initial setup for create troubleshooting doc

[Anmol1696]

No description provided.

[Anmol1696]

For the following error:

yarn starship start
yarn run v1.22.19
$ starship --config configs/local.yaml start
argv: config : configs/local.yaml
config again: [object Object]
Kubernetes cluster connection is working correctly.
helm repo add starship https://hyperweb-io.github.io/starship/
"starship" already exists with the same configuration, skipping
helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "jetstack" chart repository
...Successfully got an update from the "ingress-nginx" chart repository
...Successfully got an update from the "starship" chart repository
...Successfully got an update from the "istio" chart repository
Update Complete. ⎈Happy Helming!⎈
helm search repo starship/devnet --version 1.5.0
NAME            CHART VERSION   APP VERSION     DESCRIPTION                
starship/devnet 1.5.0           0.1.1           A Helm chart for Kubernetes
Installing the helm chart. This is going to take a while.....
helm install -f /Users/anmol/Documents/git/cosmos/hyperweb-io/hyperweb/starship/configs/local.yaml starship-devnet starship/devnet --version 1.5.0 --timeout 10m
Error: INSTALLATION FAILED: Unable to continue with install: ConfigMap "keys" in namespace "default" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "starship-devnet": current value is "starship-e2e-tests"
Error: Error: INSTALLATION FAILED: Unable to continue with install: ConfigMap "keys" in namespace "default" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "starship-devnet": current value is "starship-e2e-tests"

This means that there is already an installed helm chart, which is running in the same namespace.
Either create a new namespace, which is diff from this one, or just stop and start the chart again.

[Anmol1696]

On running kubectl get pods, if you see have too many restarts of your pods after a longer duration of time (more then 2-3 hrs), that means there is an issue with the system.

✗ kubectl get pods
NAME                        READY   STATUS    RESTARTS      AGE
cosmoshub-4-genesis-0       3/3     Running   9 (73m ago)   15h
registry-67d7c9d5f7-ngq68   1/1     Running   0             2d11h

If the age is alot, that means the memory of the nodes are already being filled: consider to increase cpu and ram for ur nodes.
Starship for local setup is not meant to be running longer running nodes, unless it is running in a k8s cluster with sufficient resources and ideally a PVC.
For local setup, please consider to stop and start starship again, creating fresh nodes.