fix(workflow-executor): self-descriptive log messages for activity log operations

[Scra3]

Summary

• Replaced opaque Activity log markSucceeded / Activity log markFailed / Activity log createPending labels with self-descriptive messages readable without field inspection
• Pattern: activity log <operation> failed for errors, "activity log <operation>" failed, retrying for retries

Before:

warn: "Activity log markSucceeded" failed, retrying
error: Failed to mark activity log as succeeded

After:

warn: "activity log mark-as-completed" failed, retrying
error: activity log mark-as-completed failed

🤖 Generated with Claude Code

Note

Standardize log message format for activity log operations in workflow-executor

Updates the withRetry operation labels and error log messages in ForestadminClientActivityLogPort to use a consistent lowercase hyphenated format (e.g. activity log create, activity log mark-as-completed failed) instead of the previous mixed-case camelCase style. Test expectations in the corresponding test file are updated to match.

^{Macroscope summarized b46209a.}

[qltysh]

Coverage Impact

This PR will not change total coverage.

Modified Files with Diff Coverage (1)

Rating	File	% Diff	Uncovered Line #s
	...-executor/src/adapters/forestadmin-client-activity-log-port.ts	100.0%
	Total	100.0%

🚦 See full report on Qlty Cloud »

🛟 Help

• Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

• Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

• File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

  • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.