enhance: add sparse float vector support to restful v2

[zhengbuqian]

issue: #29419
also re-enabled an e2e test using restful api, which is previously disabled due to #32214.

In restful api, the accepted json formats of sparse float vector are:

• {"indices": [1, 100, 1000], "values": [0.1, 0.2, 0.3]}
• {"1": 0.1, "100": 0.2, "1000": 0.3}

for accepted indice and value range, see https://milvus.io/docs/sparse_vector.md#FAQ

[mergify]

@zhengbuqian ut workflow job failed, comment rerun ut can trigger the job again.

[mergify]

@zhengbuqian E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

[codecov]

Codecov Report

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

Project coverage is 82.03%. Comparing base (32d3e22) to head (1799be6).
Report is 23 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #33231      +/-   ##
==========================================
- Coverage   82.07%   82.03%   -0.04%     
==========================================
  Files        1003     1012       +9     
  Lines      128993   128936      -57     
==========================================
- Hits       105869   105773      -96     
- Misses      19138    19171      +33     
- Partials     3986     3992       +6     

Files	Coverage Δ
...nternal/distributed/proxy/httpserver/handler_v2.go	89.16% <100.00%> (+0.01%)	⬆️
...ernal/distributed/proxy/httpserver/wrap_request.go	96.55% <92.59%> (-0.53%)	⬇️
internal/distributed/proxy/httpserver/utils.go	87.76% <90.69%> (+0.14%)	⬆️
pkg/util/typeutil/schema.go	85.94% <78.00%> (-0.27%)	⬇️

... and 215 files with indirect coverage changes

[PowderLi]

a collection can only has one sparse vector?

[zhengbuqian]

good catch, updated

[PowderLi]

I'm not sure whether #20415 will happen again when sparse vector contains int64?

[zhengbuqian]

updated the parsing function to reject out of range numbers

[mergify]

@zhengbuqian ut workflow job failed, comment rerun ut can trigger the job again.

[PowderLi]

1. is format2 forgotten? the idx(string) can only be parse to uint 32.
2. what abort format1? the idx( "indices": [?, ?, ?] ), please check the input and the result after decode

func CreateSparseFloatRowFromJSON(input []byte) ([]byte, error) {
	var vec map[string]interface{}
	decoder := json.NewDecoder(bytes.NewReader(input))
	decoder.DisallowUnknownFields()
	err := decoder.Decode(&vec)
	if err != nil {
		return nil, err
	}
	return CreateSparseFloatRowFromMap(vec)
}

[PowderLi]

as the doc described

The vector dimensions must be of Python int or numpy.integer type, and the values must be of Python float or numpy.floating type.

valid cases

• "sparseVectorFieldName": {"indices": [9223372036854775807], "values": [0.1]}}
• "sparseVectorFieldName": {"9223372036854775807": 0.1]}}

[zhengbuqian]

discussed offline and summarizing here:

the referenced doc is only to describe that we support both native Python int and numpy integer type. the accepted value range is described in https://milvus.io/docs/sparse_vector.md#FAQ. so the above 2 cases are actually invalid as the index is out of range.

[PowderLi]

/lgtm

[czs007]

/approve

[sre-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: czs007, zhengbuqian

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• internal/distributed/OWNERS [czs007]
• pkg/util/OWNERS [czs007]
• tests/OWNERS [czs007]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment