Problem: The pipeline creation wizard in BO does not check for special characters and does not redirect to the activity page of jobs with special characters.

The same constraints/rules should apply as in classic

Care must be taken to ensure valid unicode is allowed and not inadvertently blocked. ATH test coverage is a pre-req for this. 

Steps to reproduce:

1. Create a new pipeline using the BO UI
2. In the pipeline name field enter any of these:
3. file:/etc/hosts
4. Or any of the unicode special characters from here:  https://github.com/minimaxir/big-list-of-naughty-strings/blob/master/blns.txt

1. Save the pipeline.
2. At this point I got a 404
3. Next I saw that the job was in the main UI but which I clicked on it, I got another 404.
4. After I restated the jobs with the special characters disappeared from the UI.