Move repo to cert-manager/cert-manager

[meyskens]

Currently cert-manager has been operating in both the Jetstack GitHub org and the cert-manager org.
This has been causing certain limitations for a while now. However with the donation of cert-manager to a foundation it becomes more of a need to move cert-manager into the cert-manager organisation.

This is easier said than done. As it brings a lot of things to think about:

• change all Go import paths + bazel
• move our prow setup to cert-manager/testing
• set up the release tool to use the cert-manager/cert-manager repo
• ensure all redirects work
• change license boilerplate
• look into a solution for our Helm charts, do we mirror charts.jetstack.io? Do we migrate to charts.cert-manager.io?
• quay.io images

Anything I forgot?

Plan of action:

1. Move Prow and set everything up
2. Move the repos over
3. PR changes to the repo's path. Not a huge issue thanks to Go Modules anymore but still

In the first release post move:

• publish quay.io images under a new org.
• publish a helm chart repo
• update and test the release tooling

[jakexks]

/assign

[maelvls]

As per cncf/toc#557, all the "crutial" steps are done and the only step missing is to transfer the domain name cert-manager.io.

Can we proceed with the migration of https://github.com/jetstack/cert-manager to https://github.com/cert-maanger/cert-manager? Or do we have to do more things before doing so? @jakexks

[jetstack-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle stale

[jetstack-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle rotten
/remove-lifecycle stale

[SgtCoDFish]

I think this issue can be closed in favour of #3672 - just so we have one place for tracking this stuff. 👍