docs: Clarify maxDuration behavior when used with activeDeadlineSeconds. Fixes #13044

[leesungbin]

Fixes #13044

Motivation

The current documentation for maxDuration in the Argo workflow is unclear and potentially misleading, particularly when used in conjunction with activeDeadlineSeconds.
The description does not accurately reflect the behavior observed in the code, where the pod's deadline set by activeDeadlineSeconds is overridden by maxDuration upon workflow failure.

argo-workflows/workflow/controller/operator.go

Lines 1053 to 1054 in a1db80a

	woc.log.WithField("node", node.Name).Infof("node has maxDuration set, setting executionDeadline to: %s", humanize.Timestamp(maxDurationDeadline))
	opts.executionDeadline = maxDurationDeadline

This can lead to confusion for users trying to understand how these two parameters interact.
The updated documentation aims to clarify this behavior, ensuring that users have a precise understanding of how maxDuration and activeDeadlineSeconds work together in the context of workflow retries and backoff strategies.

Modifications

Updated comments in pkg/apis/workflow/v1alpha1/workflow_types.go and run make pre-commit -B.

Verification

make docs passed.