Use Random Routes in Test Applications

[hoffmaen]

The sample-app-test workflow currently fails, because someone else deployed these sample apps in his/her own CF space on the same instance. Thus, the routes are takes and cannot be reassigned to apps in our CF space.

With this change, we prefix the routes with the Workflow Run ID, which should always give us unique routes.

Side note 1: cf push comes with the optional --no-route flag, unfortunately it's not working with mta deployments. That's why we have the yq step to remove all routes from the manifest before deploying it.

Side note 2: We cannot use random-route: true in the manifest: The GRPC tests require http2, and unfortunately the protocol for random routes defaults to http1 and cannot be overwritten (unless using cf update-destination). Hence, random-route is not an option, as it would break the scenario where a user deploys the test apps.

[cla-assistant]

All committers have signed the CLA.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[peanball]

the only thing different is the path to the proto files. These files are all identical and just kept with the examples for completeness. There is no good reason to explicitly use different ones. In fact it would be better to use a single one to ensure that the examples all do the same thing and not something different.

[hoffmaen]

In fact, the grpcurl command for the go-grpc-test app differs from the remaining ones. I'd like to keep the focus on fixing the route issue in this Pull-Requst, and do other improvements separately.

[peanball]

instead of deleting, could we define a (default empty) prefix variable?

e.g.

application:
  route: "((prefix))some-app-name.((domain))"

and then define prefix: "" in the vars.yml, to override it when deploying?