Create true integration tests for Cake.Warp aliases

[AdmiringWorm]

Is your feature related to a problem? Please describe

The problem is that there currently is no integration tests that actually
checks if the cake aliases work as they should.

Desribe the solution you'd like

The ideal solution would be to run Cake itself against a dynamically created script
in the Cake.Warp.IntegrationTests library.
This would need to be able to test both during .NET/Mono version of Cake, as well as against the .NET Core edition of Cake.

Describe alternatives you've considered

Considered calling the aliases directly, but this would mean we needed to mock out some of the
classes needed for it to work. This would then mean it isn't a true integration test.

Additional context

…

[AdmiringWorm]

hmm, maybe using cake.frosting could be an option.
Something I would definitely need to consider.

[gep13]

Have you seen the integration tests that @pascalberger has just added to Cake.Issues.Reporting.Generic?

[AdmiringWorm]

I have now, but that wouldn't work as I want it.

Even for integration tests, I would still want these to be reported whether they are covered on coverage reports.
This doesn't seem to be available with the integration tests/demos that were added in that repo.

[gep13]

Ah, I see.