fix/upgrade integration tests

• tests sometimes pass despite introducing breaking changes
  • The main reason was having introduced a gyp lib that needed sudo permissions breaking the cml service inside the CML aws image managed by our terraform provider
• should use external repo & send-check to
  • avoid spamming CML with comments
  • avoid too many token permissions

We need:

• Integration tests that take the whole picture
  • testbot should do the trick however the CML image is picking from master

[DavidGOrtega]

No, what I say is that despite that we are testing everything when we launch a cloud runner it is going to use “live” cml not “dev”, hence we are not going to notice those issues and testing with cloud runners is unsecure

[0x2b3bfa0]

Not necessarily <kbd>blocked</kbd> by https://github.com/iterative/cml/issues/645 unless we plan to send GitHub checks between repositories. In fact, I would prefer to avoid that approach and resort to our jest tests instead to verify that the triggered actions have altered the target repository status in the expected way.