feat: add maxRetry and patch option

[dongjiang1989]

ref: volcano-sh/volcano#3846

[volcano-sh-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign kevin-wangzefeng
You can assign the PR to them by writing /assign @kevin-wangzefeng in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[googs1025]

Why do we need to store this field here? Can't we use the known information to get the original jobtemplate object? Or directly patch itself?

[dongjiang1989]

In my usage scenario, I still need to Patch some information to replace the content of the JobTemplate. Avoid partial differences causing an explosion in the number of JobTemplates.
User case:

apiVersion: flow.volcano.sh/v1alpha1
kind: JobTemplate
metadata:
  name: a
spec:
  tasks:
    - spec:
          containers:
            - image: tf2.16-cuda11-xxx:v1.0.1
              command:
                - sh
                - -c
                - ./script.py --dateset a.txt --mode 1
              imagePullPolicy: IfNotPresent
              name: nginx
              resources:
                requests:
                  cpu: "1"
          restartPolicy: OnFailure
---
apiVersion: flow.volcano.sh/v1alpha1
kind: JobFlow
metadata:
  name: test-flow1
  namespace: default
spec:
  jobRetainPolicy: delete
  flows:
    - name: a
---
apiVersion: flow.volcano.sh/v1alpha1
kind: JobFlow
metadata:
  name: test-flow2
  namespace: default
spec:
  jobRetainPolicy: delete
    - name: a
      patch:
          spec:
             tasks:
               - spec:
                     containers:
                        - image: tf2.16-cuda11-xxx:v1.0.2 # just different image
                           command:
                              - sh
                              - -c
                              - ./script.py --dateset b.txt --mode 2 # just different args

[googs1025]

sorry for this. I don't see what patch does. It seems to make the whole cr configuration more complicated.

[hwdef]

It doesn't look good. How about just adding a maxRetry field?

[hwdef]

type Flow struct {
	// +kubebuilder:validation:MinLength=1
	// +required
	Name string `json:"name"`
	// +optional
	DependsOn *DependsOn `json:"dependsOn,omitempty"`
	// +optional
	MaxRetry *MaxRetry `json:"maxRetry,omitempty"`
}

[dongjiang1989]

It doesn't look good. How about just adding a maxRetry field?

Thanks @hwdef @googs1025
Got it. Just add maxRetry field done.