removal of dpath -- ready for review

[dafnapension]

Hi Elron and Yoav,
d_path is out of dict_utility, and of both requirement files where it showed.

I also cancelled the ban of process_every_value not allowed for operator RemoveValues (a ban laid only on it..)
We do need process_every_value here.

Speaking of which (the family of field operators, including all the postprocessors, that process a (single) prediction and process every value of list of references), why is EncodeLabels so much of an outsider?
There is a straightforward implementation thereof as a field operator. Why was not it used?

[codecov]

Codecov Report

Attention: Patch coverage is 93.58974% with 20 lines in your changes are missing coverage. Please review.

Project coverage is 89.95%. Comparing base (93dc8d4) to head (3d0f6ff).

Files	Patch %	Lines
src/unitxt/dict_utils.py	90.38%	20 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #680      +/-   ##
==========================================
+ Coverage   89.83%   89.95%   +0.11%     
==========================================
  Files          96       96              
  Lines        9201     9419     +218     
==========================================
+ Hits         8266     8473     +207     
- Misses        935      946      +11     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dafnapension]

@elronbandel , @yoavkatz , I suggest to remove the boolean parameter set_multiple from dict_set.
If the * comes at the end of the query, the same result can be achieved by assigning a whole vector (for arg value of dict_set()) to the parent of the * in the query; and if the * comes in the middle of the query, it is not always clear that the meaning was breaking the input value (the vector) into its individual components, and assign one component to each path, rather than the whole of value to each and every path.
It is also not clear what should happen with more than one * on the query.

Other than enjoying to play with it in the testing, I do not see any real value for this set_multiple parameter.

Again: the meaning thereof is clear if * comes at the end, but the same result is achievable by assigning the whole vector as one unit, to the parent of the * in the query.

The meaning thereof for * in the middle of the query was guessed by myself, and thus implemented.. You may see some examples in test_dict_utils.

I wrote extended docstring for dict_set. Please see if this looks clear enough.

[elronbandel]

This is amazing Dafna! I think any comments on top of this implementation should be in a seperate PR as this one defentily satisfy its original goal! well done!