ux: forc index deploy should not panic when unable to connect to fuel-indexer

[lostman]

Description

Currently, forc index deploy panics when it is unable to connect to fuel-indexer:

▹▹▹▹▸ ⏰ Building indexer...
Finished release [optimized] target(s) in 0.19s
▪▪▪▪▪ ✅ Build succeeded.
Deploying indexer...
▸▹▹▹▹ 🚀 Deploying...
thread 'main' panicked at /Users/mw/Data/Code/Work/FuelLabs/fuel-indexer/plugins/forc-index/src/ops/forc_index_deploy.rs:133:10:
Failed to deploy indexer.: reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Ipv4(127.0.0.1)), port: Some(29987), path: "/api/index/mw/some_indexer_2", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 61, kind: ConnectionRefused, message: "Connection refused" })) }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
zsh: abort      forc-index deploy

We should print something more user friendly.