ODataService.request: removing all @odata metadata fields was a wrong decision

[buchatsky]

First, if it is done, is should be done recursively, not only on single entity, but also on arrays.
And second, it should not be done at all, because e.g. @odata.etag is required for optimistic concurrency when RowVersion field is not included in $select clause or is not present in DTO model.
Presence of odata metadata in response should be controlled by "metadata" param of "accept" http header. It may be a param in ODataService constructor

[AimTune]

Recent changes did not take effect in the npm package. You can check out the example below.

[buchatsky]

It probably fixed the contradiction between github and npmjs sources, but not the issue with functionality itself.
pr#82 fixes it (preserves odata metadata in the resulting object)

[AimTune]

It probably fixed the contradiction between github and npmjs sources, but not the issue with functionality itself. pr#82 fixes it (preserves odata metadata in the resulting object)

The npm package is not updated because the npm token is not defined under Github Actions Secrets.

[buchatsky]

@AimTune That was not the point of this issue. The point was to remove back the code that cleared metadata and leave it as it was before