create yank-buildpack command

[elbandito]

Summary

**NOTE: In the RFC, there is mention of 2 types to support: github and git. This PR is ONLY for supporting github.

This PR introduces the new pack yank-buildpack command (hidden behind the experimental flag). This command is used to update a previously registered buildpack as yanked inside the Github registry . If the user wants to undo a previously yanked buildpack from the registry, they can use the --undo flag. In both cases, the command will open a new browser window to create/submit a Github Issue (see below).

> pack yank-buildpack heroku/rust@1.2.3

> pack yank-buildpack heroku/rust@1.2.3 --undo

Output

pack yank-buildpack --help
yank the buildpack from the registry

Usage:
  pack yank-buildpack <buildpack-id-and-version> [flags]

Flags:
  -r, --buildpack-registry string   Buildpack Registry name
  -h, --help                        Help for 'yank-buildpack'
  -u, --undo                        undo previously yanked buildpack

Global Flags:
      --no-color     Disable color output
  -q, --quiet        Show less output
      --timestamps   Enable timestamps in output
  -v, --verbose      Show more output

For more details on the flow of this command and how it's used, see the RFC.

Documentation

• Should this change be documented?
  • Yes, see #___
  • No

Related

Resolves #___

[codecov]

Codecov Report

Merging #754 into main will increase coverage by 0.15%.
The diff coverage is 82.76%.

@@            Coverage Diff             @@
##             main     #754      +/-   ##
==========================================
+ Coverage   73.53%   73.67%   +0.15%     
==========================================
  Files          75       77       +2     
  Lines        5103     5184      +81     
==========================================
+ Hits         3752     3819      +67     
- Misses       1037     1048      +11     
- Partials      314      317       +3     

Flag	Coverage Δ
#os_linux	76.15% <84.06%> (+0.13%)	⬆️
#os_macos	72.08% <84.06%> (+0.19%)	⬆️
#os_windows	72.05% <82.76%> (+0.17%)	⬆️
#unit	73.67% <82.76%> (+0.15%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[dfreilich]

A few nits, but overall this is great! Definitely appreciate the efforts at testing in this one

[jromero]

@elbandito, @dfreilich left a few comments. I'm eager to run through acceptance to get this in but want to wait for those conversations to be resolved so that it doesn't happen in vain if a few things might change. Let me know if I should proceed anyway.

[elbandito]

@elbandito, @dfreilich left a few comments. I'm eager to run through acceptance to get this in but want to wait for those conversations to be resolved so that it doesn't happen in vain if a few things might change. Let me know if I should proceed anyway.

Thanks for the comments @dfreilich!
@jromero let me make some changes first then I'll give you the heads-up.

[elbandito]

@jromero I made some changes. It's now ready for you to run some UA tests.

[jromero]

@elbandito I'm not sure if you've seen some minor unresolved test related comments from @dfreilich (they may be hidden by default in the GitHub UI). Going to start UA, just thought I'd mention it in case they were missed.

[elbandito]

@dfreilich did you have anything else you'd like for me to address before approving? I did pass on the godoc nits for this PR, but happy to look into them later.

[dfreilich]

@elbandito It generally looks great. If you could add a test or two for GetIssueURL though, it would be nice (though it's simple, it's nice to have it be tested anyways in case it grows more complex)

[elbandito]

GetIssueURL

@dfreilich sorry, must have missed that comment. The test has been added.