update chainlink-sui for 2.55.5

[FelixFan1992]

Requires

Supports

[github-actions]

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[github-actions]

✅ No conflicts with other open PRs targeting release/2.55.5

[github-actions]

CORA - Pending Reviewers

Codeowners Entry	Overall	Num Files	Owners
*	⏳	1	@smartcontractkit/foundations, @smartcontractkit/core
/core/capabilities/	⏳	2	@smartcontractkit/keystone, @smartcontractkit/capabilities-team
/core/services/workflows/	⏳	14	@smartcontractkit/keystone
go.md	⏳	1	@smartcontractkit/core, @smartcontractkit/foundations
go.mod	⏳	6	@smartcontractkit/core, @smartcontractkit/foundations
go.sum	⏳	6	@smartcontractkit/core, @smartcontractkit/foundations
integration-tests/go.mod	⏳	1	@smartcontractkit/core, @smartcontractkit/devex-tooling, @smartcontractkit/foundations
integration-tests/go.sum	⏳	1	@smartcontractkit/core, @smartcontractkit/devex-tooling, @smartcontractkit/foundations

Legend: ✅ Approved | ❌ Changes Requested | 💬 Commented | 🚫 Dismissed | ⏳ Pending | ❓ Unknown

For more details, see the full review summary.

[trunk-io]

     

Failed Test	Failure Summary	Logs
TestToCanonicalJSON_OmitsEmptyFields/nested_empty_string_and_empty_repeated_field	The test failed because the actual JSON output included an unexpected 'requestId' field that was not present in the expected output.	Logs ↗︎
TestToCanonicalJSON_OmitsEmptyFields/empty_repeated_field_and_empty_top-level_string	Test failed because the actual output included an extra 'requestId' field that was expected to be omitted.	Logs ↗︎
TestToCanonicalJSON_OmitsEmptyFields/empty_repeated_field_only	The test failed because the actual output included an unexpected 'requestId' field that was not in the expected output.	Logs ↗︎
TestToCanonicalJSON_OmitsEmptyFields	The test failed without providing specific error details, indicating an unspecified failure in the test case.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube