chore: reduce chance of flakiness on the migrate integration test

[josephschorr]

Adds retries and increases the wait timeout for the migration call

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.45%. Comparing base (e55404b) to head (d14152b).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2674      +/-   ##
==========================================
- Coverage   79.46%   79.45%   -0.00%     
==========================================
  Files         455      455              
  Lines       47161    47161              
==========================================
- Hits        37470    37467       -3     
+ Misses       6945     6944       -1     
- Partials     2746     2750       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[miparnisari]

why do we even have a timeout here..? i say let the thing take as long as it wants: remove the retry stuff and the waitCtx.

[josephschorr]

I don't want the test to hang

[miparnisari]

it won't hang, that's what go test -timeout XXX is for: https://github.com/authzed/actions/blob/main/go-test/action.yaml#L11

ugh we don't use that action for these. can you add -timeout 20m to

spicedb/magefiles/util.go

Lines 42 to 51 in 03a31da

	func testWithArgs(ctx context.Context, args ...string) ([]string, error) {
	testArgs := append([]string{
	"test",
	"-failfast",
	"-count=1",
	"-race",
	}, args...)
	return testArgs, nil
	}

?

Also FYI, github actions have a default timeout of 360 minutes per step.

[josephschorr]

Closing in favor of #2696