Container Service: deprecate older versions of containerServices endpoints

`Microsoft.ContainerService/stable/2017-07-01` deprecated the following paths:

```
/subscriptions/{subscriptionId}/providers/Microsoft.ContainerService/containerServices
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerService/containerServices/{containerServiceName}
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerService/containerServices
```

and they never appear in later versions.

Should they also be deprecated in older versions? (`2016-03-30`, `2016-09-30`, `2017-01-31`, etc.)

Locate the Microsoft.ContainerService REST API specifications for 2016-03-30, 2016-09-30, 2017-01-31, and the later 2017-07-01 version, then compare the three listed containerServices paths. Check how deprecation is represented in the existing specification and confirm that the older versions still expose these paths; done means the affected versions consistently reflect their deprecated status.

Written by the indexing model from the issue text.