RD-1207558 | Binary Build Requirements Compliance

[dev-menon]

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.

[github-actions]

Thank you for your submission! We really appreciate it. Like many source-available projects, we require that you sign our Contributor License Agreement (CLA) before we can accept your contribution.

You can sign the CLA by posting a comment with the message below.

---

I have read the Contributor License Agreement (CLA) and I hereby sign the CLA.

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[fivetran-anushkaparashar]

Changes look good to me!

[fivetran-anushkaparashar]

@dev-menon Please check failing tests in the pipeline and resolve conflicts.

[antiguru]

It seems the fivetran destination doesn't exist anymore in this repo, #36919. Closing the PR. Please re-open if needed.

[def-]

@dev-menon I have rebased the PR on latest main. Can you please sign the CLA? Otherwise LGTM