Add Create and Edit and run features for CustomRuns

[jisoolee]

Changes

The adding Create and Edit and run features for CustomRuns task and it is subdivided into 3 parts (will have 3 different commits per each part in one PR)

• Part1. Adding Create and Edit and run buttons
• Part2. Creating a Create page + Connecting the buttons to the proper Create/EditAndRun pages
• Part3. Adding test cases

Part1. Adding Create and Edit and run buttons

Part2. Creating a Create page + Connecting the buttons to the proper Create/EditAndRun pages

Part3. Adding test cases

Connect to #2437

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

NONE

[tekton-robot]

Hi @jisoolee. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[AlanGreene]

Thanks @jisoolee. We need to make sure the Dashboard is always in a releasable state, so we'll either need to hide the buttons behind some kind of feature flag (query param or localStorage), or hold this PR until the create / edit page is merged first.

[jisoolee]

@AlanGreene Thank you for review and comment. I understand, yes I was also worrying about the release schedule (if I could not completed all the tasks before the next release). Please hold this PR until I complete the feature.

[AlanGreene]

/hold

[AlanGreene]

There's a lot of code in this related to the form-based UI which we are not adding for CustomRuns. Once that's removed there may be some opportunities to simplify / cleanup the remaining code.

[AlanGreene]

There's still quite a bit of unused code here that needs to be removed. I've added comments to the biggest pieces.

Most of this should have been caught by the linter so I'll have to debug that to figure out why it's not reporting errors.

For now you'll have to manually review each function, variable, and state field you've added to ensure they're actually used, and remove any that are not needed. When you remove a function, for example handleSubmit, check if there are additional functions or variables that can be cleaned up following its removal.

[AlanGreene]

For tracking purposes:

The issue with the linter not reporting issues was identified and resolved in #3139

[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

[briangleeson]

/hold cancel

[briangleeson]

/ok-to-test