Remove CLA Requirement and Remove obsolete PR builder link

[oleg-nenashev]

This is a follow-up to the JENKINS-50216 discussion with @tcnghia in the email threads. According to this discussion, CLA is no longer required.

This PR needs to be integrated in order to unblock JEP-200 maintainers.

CC @reviewbybees @jglick

[oleg-nenashev]

@astroilov What are the next steps here? We cannot propose JEP-200 fixes until it is integrated into the master

[astroilov]

It appears that I no longer have write access, meaning I cannot merge this PR (or the actual fix PR that you have sent). I will see if I can find another reviewer that does have write access among those who've worked on this plugin. If it was accidentally "owner-orphaned", we may need to contact one of the owners of the jenkinsci org.

[oleg-nenashev]

@astroilov It is easy to fix, because I am one of admins. We were doing permission cleanup this February: https://groups.google.com/forum/#!msg/jenkinsci-dev/ksKAsmsmVng/xHyym1fYAAAJ;context-place=forum/jenkinsci-dev, so likely you lost permissions during it (you were getting them from the Everyone group).

Restored your permissions, please let me know whom I should also add to this plugin or other plugins Google maintains

[daniel-beck]

@oleg-nenashev Not quite. The permissions for this repo were granted via the oauth-credentials-developers team during a time we hadn't locked down what regular users could do, and some used that to make an absolute mess of per-repo teams. That was a separate cleanup. See the audit log.

[oleg-nenashev]

Now there is a single team with "Write" permission. Should be fine, right?

[astroilov]

Ah, that does make things easier! Thanks!