Allow views to be targeted in form based activities

[#1]

Description -
Currently to target a triggerView() call, widely used in SPAs you have to use the VEC. This can be very cumbersome and the VEC is not always supported by user's website setups, making it difficult or impossible to build activities with triggerView. Ideally we would be able to select view names in the Location dropdown of a form based activity so that we can target views without having to manually reach them in the VEC. This would also be useful for tests which span multiple locations and cover both mboxes and views. 

Why is this feature important to you - A large part of my website is a React SPA, in order to build tests for some components I have to go through my entire SPA which can take upwards of ten minutes to trigger the view I want to target. I only use target as a code delivery tool rather than using the VEC, so form based activities are much more suitable, but can't be used at the moment with views. Also, the VEC is fairly unreliable and often breaks my site so that I can't progress to the view in the first place, making it impossible to test certain components which massively increases frustration and decreases usability.

How would you like the feature to work - In form based activities when you add a location, simply add user's view names to the Location dropdown as well as mboxes. Then a user can target both or either of mboxes and views in a single form based activity while avoiding the VEC.

Current Behaviour - Users have to use the visual editor to target views, which is clunky, unreliable, and adds frustration as the user is required to manually trigger the view through the VEC window even if they are not making an edit in the visual editor. Form based activities can only target mboxes.