Automate with Rancher GitRepoRestrictions not defaulting the GitRepo

[mmartin24]

Ref: https://github.com/rancher/fleet/issues/3077#issuecomment-2479006039
QASE: https://app.qase.io/case/FLEET-153

Considerations:

• Cypress issue executing kubectl in subshell.
  • Possible workaround: to execute in UI.
  • Also follow up resolution onhttps://github.com/rancher/fleet-e2e/compare/main...fleetqa/webhook-basic-test#diff-939d6b943c112610cdef9a3b9be1[…]578c146223fbf7c16f12df34aa92c7R50 as it encountered the same issue.
  • Maybe can be skiped adding service account on downstream cluster as main check to be done will be on the job to ensure the value serviceaccount points to the restricted one previously defined. (Check ticket or QASE ticket for ref)