Update timeout support for CreatePipelineRun and CreateTaskRun

[AlanGreene]

Changes

PipelineRun.spec.timeout was deprecated in Pipelines v0.36.0, and replaced with a new PipelineRun.spec.timeouts which allows setting timeouts for the entire pipeline, for its tasks, for finally tasks, or any combination of these.

Update the UI to provide the additional input fields for the new values and remove the existing validation as these fields are not specified as numeric values representing minutes, instead they support a duration syntax provided by Go's ParseDuration, e.g. 1h20m30s.

Update the CreateTaskRun page to support this format too instead of restricting the user to entering minutes.

Fix some redundant 'optional' labels on input fields.

/kind feature

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Docs included if any changes are user facing
• Tests included if any functionality added or changed
• Follows the commit message standard
• Meets the Tekton contributor standards (including
  functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• Release notes block below has been updated with any user facing changes (new features, significant UI changes, API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

Update the timeout field on the Create PipelineRun and Create TaskRun pages to support the duration format, e.g. `1h20m30s`. Add support on the Create PipelineRun page for the `timeouts.pipeline`, `timeouts.tasks`, and `timeouts.finally` fields introduced in Pipelines v0.36.0.

[briangleeson]

I see there's no validation on timeouts or helper text. Format looks to be like 0h0m60s, so not sure what happens if you provide a bad value? Worth validating by regex or adding help text for the format?

[AlanGreene]

Validation is performed by the Tekton controller and returned in a notification on the page. There's more to the validation than just the format as certain combinations of values are not allowed, also depending on the default global config.

[briangleeson]

/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: briangleeson

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [briangleeson]

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