docs: fix ttlSecondsAfterFinished indentation in examples 11 and 13
What type of PR is this?
/kind docs
What this PR does / why we need it:
Examples 11 (Linear webhook) and 13 (generic webhook) placed ttlSecondsAfterFinished at the spec level alongside maxConcurrency. Because the field is only defined on TaskTemplate and not on TaskSpawnerSpec, Kubernetes silently dropped it. Users following these examples never had their spawned Tasks auto-cleaned up, even though they believed they had configured a TTL.
This re-indents the field one level deeper so it sits inside taskTemplate, matching the placement used in the working examples (03, 04, 06, 10, 12).
Which issue(s) this PR is related to:
Fixes #1137
Special notes for your reviewer:
Pure YAML re-indent in two example files. No code or schema changes.
Does this PR introduce a user-facing change?
NONE
Summary by cubic
Moved ttlSecondsAfterFinished into taskTemplate in examples 11 (Linear webhook) and 13 (generic webhook) so TTL cleanup works and spawned Tasks auto-delete as intended. Fixes #1137.