build(deps): bump github.com/alexflint/go-arg from 1.4.3 to 1.5.1

[dependabot]

Bumps github.com/alexflint/go-arg from 1.4.3 to 1.5.1.

Release notes

Sourced from github.com/alexflint/go-arg's releases.

v1.5.1

• Fixes a bug introduced in v1.5.0 where bad struct tags and other parser-level initialization problems would result in a crash rather than a clean exit in MustParse (thanks @​hhromic !)

Version 1.5.0

• Argument structs can define Description() and Epilogue(), which are added to the usage string

• Subcommands can have multiple aliases like this:

var args struct {
    Remove *struct{} `arg:"subcommand:remove|rm|r" help:"remove something from somewhere"`
}

• Improves formatting of usage string when the placeholder tag is set to empty string

• Do not handle --version when the args struct lacks a Version() function

• Add StructSubcommands to Config struct

Commits

• bee5cf5 Merge pull request #255 from hhromic/fix-254
• aa844c7 Fix crash on errors in package-level MustParse
• dfca71d Merge pull request #243 from alexflint/handle-empty-placeholder
• 188bd31 Merge pull request #244 from alexflint/restore-100pct-coverage
• 8a91726 add a test case with single-level subcommands
• 3ddfffd add test for help and usage when a --version flag is present
• 68948b2 restore 100% code coverage
• be792f1 ping
• 8e35a4f handle explicit empty placeholders
• bf629a1 Merge pull request #231 from alexflint/subcommand-aliases
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign mshaposhnik for approval. For more information see the Kubernetes Code Review Process.

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

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a konflux-ci 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-sigs/prow repository.