Remove POST implementation of put

[RKrahl]

Just noticed the following in the documentation:

This is an alternative to using PUT on the put resource. All the same arguments appear as form fields. In addition there are two boolean fields wrap and padding which should be set to true as a CORS work around. These two fields will be removed shortly as they are only required by the old (GWT based) topcat.

It is years now that the old (GWT based) topcat is not in use any more, but these fields are still in the code. 😲

Check whether anybody still needs that and remove it if not.

[RKrahl]

As an alternative we might consider to remove the POST implementation of the put call altogether. Need to be discussed in the collaboration.

[RKrahl]

Discussed in today's collaboration meeting: we rather consider to remove the POST implementation of the put call altogether. I will announce that again to the mailing list and if no one objects, we will deprecate that call now and remove it in 3.0.0.

[RKrahl]

Now formally deprecated in v2.1.1.