switch from languages= to language in url

Here is my suggestion for APIs with separate language versions based on URL.

* removed the languages= section because its primary use would be the same: select only a single language to be returned.
* maintained the same format with languages nested in objects to clearly mark language content and to make implementing and combining both methods easier
* require a known URL pattern to move between languages instead of adding fields to metadata