chore: remove redundant cargo config file (#324)

## Summary

- Remove .cargo/config.toml that was unintentionally overriding release
and **production** profile settings
  - Fix outdated comment referencing Moonbeam instead of Datahaven

  ## Details

- The `operator/.cargo/config.toml` file was overriding the release
profile configuration defined in `Cargo.toml`. Removing it ensures the
intended `Cargo.toml` settings are used.
- The protocol = "sparse" setting for crates.io is no longer needed as
it has been the default since Cargo 1.70 (Rust 1.70.0).

## Important

This override also affected the production profile . Since
`[profile.production]` inherits from release, the `opt-level = 2` from
`config.toml` propagated to production builds.

---------

Co-authored-by: Steve Degosserie <723552+stiiifff@users.noreply.github.com>

operator/.cargo/config.toml

@@ -1,6 +0,0 @@
-[profile.release]
-lto = "thin"
-opt-level = 2
-
-[registries.crates-io]
-protocol = "sparse" 

operator/Cargo.toml

@@ -379,7 +379,7 @@ lto = true
 [profile.release]
 debug-assertions = true # Enable debug-assert! for non-production profiles
 opt-level = 3
-# Moonbeam runtime requires unwinding.
+# Datahaven runtime requires unwinding.
 panic = "unwind"
 
 [profile.testnet]