fix: send maxRetries property when it is specified by the user in a cloud run job manifest

[renzodavid9]

Fixes: #9452

Description
With this change, we'll force the inclusion of the maxRetries property whenever it's explicitly specified in a Cloud Run Job manifest, even if its value is 0. Only when it's not specified in the manifest will it be omitted, and Cloud Run will set its default value to 3.

When unmarshalling manifests into run.Job (google.golang.org/api/run/v1), the spec.template.spec.template.spec.maxRetries field is mapped to a non-pointer int64. This makes it impossible to distinguish between a 0 value from an unspecified property in the manifest and a 0 value explicitly set by the user. With this logic, we check the manifests to determine if the property was explicitly set.

[codecov]

Codecov Report

Attention: Patch coverage is 57.14286% with 9 lines in your changes missing coverage. Please review.

Project coverage is 63.15%. Comparing base (290280e) to head (4e3e108).
Report is 1166 commits behind head on main.

Files	Patch %	Lines
pkg/skaffold/deploy/cloudrun/deploy.go	57.14%	6 Missing and 3 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9475      +/-   ##
==========================================
- Coverage   70.48%   63.15%   -7.34%     
==========================================
  Files         515      645     +130     
  Lines       23150    33262   +10112     
==========================================
+ Hits        16317    21006    +4689     
- Misses       5776    10628    +4852     
- Partials     1057     1628     +571     

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