Fix: Handle max retries in awaitWorkflowResult

[vr-varad]

Fixes #143

[vr-varad]

@maxdml Kindly review at your convenience.
Would you like me to add tests as well?

[maxdml]

@maxdml Kindly review at your convenience. Would you like me to add tests as well?

Thanks Varad, yes let's fix the TestWorkflowQueues/QueueWorkflowDLQ test. All the handles calls to GetResult should yield the max retries error now. (Because the mere fact of attempting to recover the workflow moves it to the DLQ and sets the error.)

[maxdml]

see #190 (comment)

[vr-varad]

But if we look at the failing tests, not all handles are returning an error. // @maxdml
(https://github.com/dbos-inc/dbos-transact-golang/actions/runs/19861284355/job/56911788635?pr=190#step:11:2082)

[maxdml]

But if we look at the failing tests, not all handles are returning an error. // @maxdml (https://github.com/dbos-inc/dbos-transact-golang/actions/runs/19861284355/job/56911788635?pr=190#step:11:2082)

This is because the workflow is eventually allowed to complete, using dlqCompleteEvent.Set(). When the workflow function returns, it overwrites the status to success. This is expected for now. Let's just do:

1. Test all handles, they should error
2. unstuck the workflow with dlqCompleteEvent.Set()

[vr-varad]

I have made the required changes, kindly review // @maxdml
Not aware of why the security checks are failing, is it related to go version?

[maxdml]

I have made the required changes, kindly review // @maxdml Not aware of why the security checks are failing, is it related to go version?

vuln check are fixed now (I rebased your branch on top of main)

[vr-varad]

Made the changes // @maxdml