Depend on official Pandorica repo

[GiselleSerate]

Depending on Some Ex-Intern's repository isn't the most security-safe practice. (I mean, what if I deleted it? I'm not going to delete it. But you can't depend on that.)

Here's how you move Pandorica over to an official public Palo Alto Networks repo.

• Move code to new Pandorica repo under Palo Alto Networks specific repo.
  If you clone the repo locally and add the empty PAN repo as a remote, you should just be able to push all my branches to the new empty PAN repo individually. This will preserve my commit history. (Unless you don't want my commits, in which case you could literally copy paste all my code into the empty repo and add it all as one commit, but then you'd need to recreate my branches and stuff.)
• Make run_pandorica on the Jenkins server pull the Jenkinsfile from the PAN repo instead of this repo. This means that future autoruns will use the new instructions instead of whatever happens to be on master in this repo.
• Make test_pandorica on the Jenkins server pull the Jenkinsfile (changing this should also change where the code is pulled from) from the PAN repo instead of this one. This means that the test will check the new repo for changes and test them.
• Make the test Jenkinsfile specify to set commit statuses on the new repo instead of this repo. (If you do the previous step but not this one, Jenkins may complain that the repo doesn't have the commit associated with the hash specified and can't set its commit status, since it's getting changes from the PAN repo but trying to set commit statuses in this repo. Or maybe it'll fail silently. I haven't tried this yet, so I don't know.)
• Move wiki.
  We need documentation.
• Move issues/PRs.
  Including this one.