refactor(graphql-client): standardize query_types structure, naming, and extract common module

[MrSufferer]

Problem Statement

The iota-sdk-graphql-client crate (specifically the query_types module) had outgrown its original structure:

• query_types/mod.rs was heavily bloated (~200 lines), mixing exports, scalar definitions, shared structs, and implementations.
• QueryVariables types were inconsistently named (BalanceArgs vs PackagesQueryArgs).
• Individual query files lacked a consistent organizational structure.
• MovePackageQuery and TransactionsFilter were misleadingly named (the former is a GraphQL fragment, the latter represents a singular filter, not plural).
• The execute_tx.rs file existed unnecessarily, isolating transaction execution types away from the core transaction.rs domain.

Solution

This PR executes a pure structural and naming refactor across the query_types/ and api/ modules. There are no logic or runtime business-behavior changes.

Specifically, this PR:

1. Extracts query_types/common.rs: Moved all scalars (Base64, BigInt, DateTime, etc.), shared fragments (GQLAddress, MoveObject, etc.), and conversions out of mod.rs. mod.rs is now strictly a barrel file containing only mod, pub use, and backward-compatibility aliases.
2. Standardizes Naming: Renamed 18 QueryVariables types to follow a consistent {Entity}QueryArgs pattern (e.g., BalanceArgs → BalanceQueryArgs, EpochArgs → EpochQueryArgs).
3. Standardizes File Layout: Applied consistent section headers across all 18 query_types/*.rs files (Queries → Query Args → Types → Conversions).
4. Renames Misleading Types:
   • Renamed MovePackageQuery to MovePackage in packages.rs.
   • Renamed TransactionsFilter to TransactionBlockFilter in transaction.rs.
5. Consolidates execute_tx: Moved the contents of execute_tx.rs into transaction.rs and deleted the standalone file, centralizing transaction types.
6. Cross-Crate Updates: Updated iota-sdk-ffi (bindings) and the iota-sdk/examples workspace members so they compile successfully against the newly renamed graphql types.
7. Resolves Upstream Conflicts: Resolves integration conflicts with upstream/develop regarding TransactionBlockFilter parameter renaming.

Backward Compatibility

Since this library is public, we cannot simply break downstream consumers who are using the old type names. To preserve backward compatibility, deprecated type aliases have been added to query_types/mod.rs.

• Downstream users will get a deprecation warning telling them the new struct name (e.g., warning: use of deprecated type alias 'BalanceArgs': renamed to BalanceQueryArgs).

Testing

• Unit Tests: cargo test -p iota-sdk-graphql-client passes cleanly.
• Integration Tests: NETWORK=testnet cargo test --all-features -p iota-sdk-graphql-client passes cleanly.
  • Note: 2 view call tests fail expectedly because viewCall mutations are currently unsupported on the IOTA testnet infrastructure.
  • Fixed two fragile tests (test_transaction_data_effects and test_transactions_data_effects) that were panicking due to relying on hard-coded devnet digests that had gone stale. They now reliably fetch live digests.
• Bindings & FFI: cargo check -p iota-sdk-ffi successfully compiles against the type aliases.
• Linting: cargo clippy --all-targets --all-features throws zero warnings.

Related Issues

Resolves #512

[DaughterOfMars]

Since this library is public, we cannot simply break downstream consumers who are using the old type names.

We can do this, in fact, with a major version bump.

[MrSufferer]

Since this library is public, we cannot simply break downstream consumers who are using the old type names.

We can do this, in fact, with a major version bump.

Cool, let's remove them.

[DaughterOfMars]

Why is MovePackage renamed but not this?

[MrSufferer]

It was conflicted with the MoveModule inside normalized_move/module.rs.
Do you want the MoveModuleNode instead?

[DaughterOfMars]

Not necessarily, but the whole point of this issue was to find a way to make these types consistent. I do not think that this PR is currently doing that.