fix/upgrade integration tests

[DavidGOrtega]

• 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

[0x2b3bfa0]

however the CML image is picking from master ^{[citation required]}

As far as I know, we don't do that anymore ^{[1, 2]}

[0x2b3bfa0]

testbot should do the trick however the CML image is picking from master

Do you mean that the checkbot test image is being built from the latest changes in the branch that triggered the workflow?

[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]

As per #527, I would tend to avoid integration tests whenever possible and detect these issues by resorting to simpler unit tests.