🏗 [test-case-reporting] Run gulp tasks & add flags when pushing

[Rafer45]

/cc @rcebulko @estherkim
Closes ampproject/amp-github-apps#922

EDIT: Normally, we can't tell whether or not these changes break the build (since they only run on push builds). However, manually enabling the flags for the PR build didn't break the build, as shown in the following link: https://travis-ci.org/github/ampproject/amphtml/builds/711576997

[amp-owners-bot]

Hey @rsimha! These files were changed:

build-system/pr-check/local-tests.js

[estherkim]

Nice and clean! 2 questions:

1. We run integration tests in more places - dist-tests and experiment-tests, off the top of my head. Is the idea to report those too?
2. Do you plan on adding this to our GH actions test runs?

[Rafer45]

Nice and clean! 2 questions:

1. We run integration tests in more places - dist-tests and experiment-tests, off the top of my head. Is the idea to report those too?
2. Do you plan on adding this to our GH actions test runs?

1. Depends on whether the karma reporter works for those; if it does, there should be no issue reporting them as well.
2. I should probably do that; I'm not sure, though -- some of the structure (the use of "builds" and "jobs") is Travis-dependent. I'll ping @rcebulko on this one.

[rcebulko]

Nice and clean! 2 questions:

1. We run integration tests in more places - dist-tests and experiment-tests, off the top of my head. Is the idea to report those too?
2. Do you plan on adding this to our GH actions test runs?

1. Depends on whether the karma reporter works for those; if it does, there should be no issue reporting them as well.
2. I should probably do that; I'm not sure, though -- some of the structure (the use of "builds" and "jobs") is Travis-dependent. I'll ping @rcebulko on this one.

1. Tests where we can support reporting out-of-the-box with the karma reporter should probably eventually be included, but for now settling with local tests should be sufficient.
2. Likewise, GitHub Actions test runs can and should eventually be reported, but that will likely require some tweaks to the DB to add tables for GA runs separate from Travis jobs. This may fall into Ricardo's scope depending on how much progress is made elsewhere, but generally the plan is to add support for alternate CI later on/as the alternatives are fleshed out, since we're actively experimenting.