[tink-worker] Fix use and defaulting of the max-retry flag

[detiber]

Description

Previously we were trying to fetch the wrong flag value when configuring retries for tink-worker, this PR fixes that.

Why is this needed

How Has This Been Tested?

I tested this in my Tilt/kind setup

How are existing users impacted? What migration steps/scripts do we need?

Fixes issues with using the latest tink-worker for e2e testing/deployment.

It doesn't require any changes for users or require any additional migration.

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@30f4302). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #322   +/-   ##
=========================================
  Coverage          ?   23.79%           
=========================================
  Files             ?       14           
  Lines             ?     1244           
  Branches          ?        0           
=========================================
  Hits              ?      296           
  Misses            ?      928           
  Partials          ?       20           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 30f4302...0eeb688. Read the comment docs.

[displague]

This coincides with

tink/cmd/tink-worker/cmd/root.go

Line 85 in 1009dc3

rootCmd.Flags().Int("max-retry", defaultRetryCount, "Maximum number of retries to attempt (MAX_RETRY)")