Fix naming of REST API endpoints in the OpenAPI documentation

How: Be more attentive to naming of endpoints - it is very inconsistent and misleading.

Why: Because e.g. having an endpoint called GetAllCvlValuesAsync(), which ONLY gets CVL Values for a single CVL is very misleading.

For Who: Developers implementing the REST API.

Impact: Quite big I'd say, as the REST API is a continuous source of frustration, as it from an implementation standpoint is inferior to the Remoting API.

Additional context: The given example should have been named something like GetAllCvlValuesForCvlAsync.

Please, add your suggestion and feedback above to add to the insights used by Product team when deciding priorities and direction of the Inriver PIM.