Upgrade actions/checkout

[pingsutw]

Tracking issue

NA

Why are the changes needed?

Upgrade actions/checkout and set fetch-depth to 0 to fix the CI error.

https://github.com/flyteorg/flyte/actions/runs/8876065707/job/24366874983?pr=5126

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.19%. Comparing base (5470f3f) to head (1548789).
Report is 362 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #5294   +/-   ##
=======================================
  Coverage   60.19%   60.19%           
=======================================
  Files         646      646           
  Lines       45654    45654           
=======================================
  Hits        27481    27481           
  Misses      15581    15581           
  Partials     2592     2592           

Flag	Coverage Δ
unittests-datacatalog	69.31% <ø> (ø)
unittests-flyteadmin	58.78% <ø> (ø)
unittests-flytecopilot	17.79% <ø> (ø)
unittests-flyteidl	79.30% <ø> (ø)
unittests-flyteplugins	61.94% <ø> (ø)
unittests-flytepropeller	57.32% <ø> (ø)
unittests-flytestdlib	65.75% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[pingsutw]

v3 and v2 is deprecated

[thomasjpfan]

Normally, I try to use the default force-depth: 1 and only use force-depth: 0 when the GitHub Action requires it. For this PR, can we only set force-depth: 0 for the jobs that failed on the CI logs?

[eapolinario]

Can we not use force-depth: 0? Essentially just move to v4, since the original failure in the PR description was fixed by #5298.