feat: Add TimelockConfigurer.GrantRole support for TON

[krebernisak]

No description provided.

[github-actions]

👋 krebernisak, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

[Copilot]

Pull request overview

Adds TON support for TimelockConfigurer.GrantRole by introducing TON-specific timelock role hashing and implementing the on-chain (and prepared/skipSend) GrantRole message flow.

Changes:

• Added TON TimelockRoleHash mapping to TON timelock role constants.
• Implemented TimelockConfigurer.GrantRole for TON, including deterministic query ID generation for prepared transactions.
• Added unit tests covering GrantRole success/failure cases and deterministic prepared transaction behavior.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
sdk/ton/timelock_role.go	Introduces TON role-hash lookup for sdk.TimelockRole values.
sdk/ton/timelock_configurer.go	Implements GrantRole and refactors query ID generation into a helper.
sdk/ton/timelock_configurer_test.go	Adds test coverage for the new TON GrantRole behavior.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

[cl-sonarqube-production]

Quality Gate passed

Issues
4 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
88.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (1)

sdk/ton/timelock_configurer_test.go:265

• These subtests are marked t.Parallel(), but the per-case mockSetup closures capture the parent t (e.g. ton_mocks.NewAPIClientWrapped(t)). That means multiple subtests can end up sharing the same parent *testing.T concurrently, which can cause races/flaky behavior and mis-attributed failures. Either pass the subtest t into mockSetup (preferred) or don’t run the subtests in parallel.

		t.Run(tt.name, func(t *testing.T) {
			t.Parallel()