missing go.sum entry for go.mod file in Deployments

[jamest-pin]

Creating issue as requested from Slack

Expected behavior

The deployment should run ok with no intervention.

Current behavior

I get an error

$ /pulumi-deploy-executor pulumi update --stackIdentity="pinpayments/vm-aws-go/dev" --workDir="/deployment/vm-aws-go" 
2Updating (pinpayments/dev) 
3 
4 View Live: https://app.pulumi.com/pinpayments/vm-aws-go/dev/updates/3 
5 
6 @ Updating............................ 
7 
8 @ Updating............ 
9    pulumi:pulumi:Stack vm-aws-go-dev  go: github.com/gogo/protobuf@v1.3.2 requires 
10   pulumi:pulumi:Stack vm-aws-go-dev      github.com/kisielk/errcheck@v1.5.0: missing go.sum entry for go.mod file; to add it: 
11   pulumi:pulumi:Stack vm-aws-go-dev      go mod download github.com/kisielk/errcheck 
12     pulumi:pulumi:Stack vm-aws-go-dev  error: error in compiling Go: unable to run `go build`: exit status 1 
13     pulumi:pulumi:Stack vm-aws-go-dev **failed** 1 error; 3 messages 
14 Diagnostics: 
15   pulumi:pulumi:Stack (vm-aws-go-dev): 
16     go: github.com/gogo/protobuf@v1.3.2 requires 
17      github.com/kisielk/errcheck@v1.5.0: missing go.sum entry for go.mod file; to add it: 
18      go mod download github.com/kisielk/errcheck 
19  
20     error: error in compiling Go: unable to run `go build`: exit status 1 
21  
22 Resources: 
23  
24 Duration: 10s 
25  
26 Error: Update failed: [resource plugin aws-6.0.2] installing 

Steps to reproduce

1. Connect pulumi account to Github
2. Create a new project and choose 'Get a starter project'
3. Choose Pulumi Deployments
4. Choose AWS as provider, Go as language
5. Choose Virtual Machine template
6. Populate variables and run task

Context (Environment)

It affects me learning how to use Pulumi deployments using the wizard which is supposed to work. As we're evaluating Pulumi, it affects my team's confidence in Pulumi as a robust solution.

Affected feature

"Deployments"