Add support for tag constraints when adding a package repo with kctrl

[tomkennedy513]

Describe the problem/challenge you have

I am trying to add a package repo using kctrl package repository add and I would like to make use of the .spec.fetch.imgpkgBundle.tagSelection.semver.constraints field available on the PackageRepository CRD.

Describe the solution you'd like

I would like to be able to do something like kctrl package repository add my-repo --url my-repo-without-passing-in-a-tag --semver-tag-constraints "1.8.x" which would generate something like this:

apiVersion: packaging.carvel.dev/v1alpha1
kind: PackageRepository
metadata:
  name: my-repo
spec:
  fetch:
    imgpkgBundle:
      image: my-repo-without-passing-in-a-tag
      tagSelection:
        semver:
          constraints: "1.8.x"

---

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

[rohitagg2020]

We need to also be careful that we are not accepting the tag and semver at the same time.