chore(actions): Use TW actions proxy

[sergei-boiko-trustwallet]

This pull request updates all GitHub Actions workflow files to use custom proxied actions from the trustwallet/github-actions-proxy repository instead of direct third-party actions. This change centralizes control over CI/CD dependencies, improves security, and makes it easier to manage and update action versions across the organization.

The most important changes are:

Migration to TrustWallet Proxy Actions:

• All instances of commonly used actions such as checkout, setup-java, setup-dart, gradle-build-action, rust-cache, cache, build-push-action, sccache-action, upload-artifact, and github-script have been replaced with their equivalents from trustwallet/github-actions-proxy across all workflow files, including Android, iOS, Kotlin, Flutter, Linux, Docker, Rust, WASM, and codegen workflows.

Security and Maintainability Improvements:

• Direct references to third-party actions with specific commit SHAs have been removed, reducing the risk of supply chain attacks and making it easier to update actions in the future.
• Centralized action management allows for organization-wide updates and auditing of CI/CD dependencies.

Consistency Across CI/CD Workflows:

• All workflows now use the same proxy pattern, ensuring a consistent approach to dependency management for all platforms and environments (Android, iOS, Linux, macOS, Docker, WASM, etc.).

No Functional Changes to Build/Test Steps:

• The actual build, test, and artifact upload steps remain unchanged in terms of logic; only the source of the GitHub Actions has been updated.

Preparation for Future Updates:

• By using the proxy, future updates to action versions or patches can be made centrally in the proxy repository, reducing maintenance overhead for individual workflow files.

Let me know if you have any questions about how these changes affect our CI/CD pipeline or how to work with the new proxy actions!