Since version 5.0, the view controller has supported both Content and Location as objects you view content from. This create a couple issues, like previewing the first draft of a content using a custom location view controller.

Having two very similar ways to view content items adds confusion for developers, and doesn't bring much added value.

The ez_content:viewContent controller actions must accept an optional location id. If it is passed, the location will be available for typehinting (Location $location), and part of the `$params` array. The default content controller must add it to the template as `$location`.

The UrlAlias router must be updated to use generate `ez_content:viewContent` routes with the location as an argument.
The ViewConfiguration should as much as possible be converted so that it keeps working without changes, giving developers time to adopt the new approach.