GDK setup for duo-workflow-executor

What does this merge request do and why?

Read more about the Duo Workflow architecture at https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/duo_workflow/

Read about the motivation for this work at gitlab!163704 (merged)

The Duo Workflow Executor is a Go binary that is downloaded and run from our VS Code extension when someone runs a workflow. This is a new feature that is only available internally today. At present this Go binary is downloaded from a gitlab.com releases URL. But with gitlab!163704 (merged) merged it is now possible to return the URL in our API response from a configuration in config/gitlab.yml. This means the GitLab instance can now build and include the binary in public/assets and allow people to download it from there.

This opens up new opportunities in local development as we can now develop and build the duo-workflow-executor locally and this will when we run workflows from Duo Workflow Executor locally.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Impacted categories

The following categories relate to this merge request:

• gdk-reliability - e.g. When a GDK action fails to complete.
• gdk-usability - e.g. Improvements or suggestions around how the GDK functions.
• gdk-performance - e.g. When a GDK action is slow or times out.

Merge request checklist

• This change is backward compatible. If not, please include steps to communicate to our users.
• Tests added for new functionality. If not, please raise an issue to follow-up.
• Documentation added/updated, if needed.
• Announcement added, if change is notable.
• gdk doctor test added, if needed.
• Add the ~highlight label if this MR should be included in the CHANGELOG.md.

Closes gitlab-org/duo-workflow/duo-workflow-executor#11 (closed)