Application deployments fail on OCP 4.6 if the github repo name/app name is too long because there is a limit on route url names

OCP 4.6 has imposed a limit on the name of the route. Currently we get the app name from the git repo name. If the app name is too long then the route url will fail.

We should address this in two ways:

1. Expose a variable called 'app-name' to the pipelines to allow the name of the application to be overridden. Test the provided name in setup for length and fail if the provided name is too long.
2. When the app-name is applied, check for length and trim it if necessary to prevent the length issue (this is particularly for the default name)

No files or tests are identified. Start by locating the pipeline setup and the code that derives and applies the app name from the GitHub repository; check how route names are generated on OCP 4.6. Done means an override is exposed, overly long provided names fail during setup, and default names are trimmed before deployment.

Written by the indexing model from the issue text.