RD-1207558 | Binary Build Requirements Compliance (#36901)

### Description

Standardize Rust package naming to comply with Fivetran binary build
pipeline
  

- Renamed library crate from mz-fivetran-destination to
fivetran-destination in Cargo.toml, as the Fivetran binary build
pipeline requires the package name to be exactly fivetran_destination
and builds via
cargo build --release -p fivetran_destination.
- Updated binary entry point (mz-fivetran-destination.rs) to import from
the correctly named crate (fivetran_destination:: instead of
mz_fivetran_destination::).
- Updated README to reflect the correct binary output path produced by
the pipeline (target/release/mz-fivetran-destination).

The changes have been made as per this requirements page published by
Fivetran:

https://github.com/fivetran/fivetran_partner_sdk/blob/main/development-guide/binary-build-requirements.md

### Verification
Verified with using the current branch to build the binary using
pipeline and it succeeded.
<img width="470" height="426" alt="Screenshot 2026-06-07 at 8 48 17 PM"
src="https://github.com/user-attachments/assets/8ac4b06c-8d07-4d1a-8ed7-5c077a1eedf6"
/>

Author: dev-menon

Cargo.lock

@@ -1,5 +1,5 @@
 [package]
-name = "mz-fivetran-destination"
+name = "fivetran_destination"
 description = "Fivetran destination for Materialize."
 version = "0.0.0"
 edition.workspace = true

src/fivetran-destination/Cargo.toml

@@ -23,14 +23,14 @@ for instructions.
 To build the destination into a static Rust binary, run:
 
 ```shell
-cargo build --release -p mz-fivetran-destination
+cargo build --release -p fivetran_destination
 ```
 
 > **Note:** If you already have [`protoc`](https://grpc.io/docs/protoc-installation/) installed
 and in your PATH, you can skip building the vendored version with:
 
 ```shell
-cargo build --release -p mz-fivetran-destination --no-default-features
+cargo build --release -p fivetran_destination --no-default-features
 ```
 
 Cargo will emit the built binary at

src/fivetran-destination/README.md

@@ -9,8 +9,8 @@
 
 //! Fivetran destination for Materialize.
 
-use mz_fivetran_destination::logging::FivetranLoggingFormat;
-use mz_fivetran_destination::{DestinationConnectorServer, MaterializeDestination};
+use fivetran_destination::logging::FivetranLoggingFormat;
+use fivetran_destination::{DestinationConnectorServer, MaterializeDestination};
 use mz_ore::cli::{self, CliConfig};
 use mz_ore::error::ErrorExt;
 use socket2::{Domain, Protocol, Socket, Type};