Add e2e-skipper* files for test setup
It does the following things:
* install Skipper ingress with Kustomize
* load Flagger image onto the local cluster
* install Flagger and Prometheus in the flagger-system namespace
Te be able to distinct Skipper routes we need to combine the Canary data to generate the Skipper metric label.
"request-success-rate" and "request-duration" queries are implemented and tested that provide those obersvations from Skipper metrics
* Takes into account how Skipper renders the paths accordingly and reformats the quieries.