fix(exporter-collector): wrong data type for numbers

[kudlatyamroth]

Which problem is this PR solving?

It corrects data type send to collector
as of now it sends:

attributes:
 http.status_code: DOUBLE(200)

and should be:

attributes:
 http.status_code: INT(200)

Short description of the changes

Add way to select intValue in toCollectorAnyValue only for numbers that qualify to range of INT and Number.isInteger()

[linux-foundation-easycla]

The committers are authorized under a signed CLA.

• ✅ Karol Fuksiewicz (96c6f79, bc9d827)

[codecov]

Codecov Report

Merging #1938 (8f359dc) into main (167bfd8) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #1938   +/-   ##
=======================================
  Coverage   92.89%   92.90%           
=======================================
  Files         152      152           
  Lines        5914     5922    +8     
  Branches     1240     1245    +5     
=======================================
+ Hits         5494     5502    +8     
  Misses        420      420           

Impacted Files	Coverage Δ
.../opentelemetry-exporter-collector/src/transform.ts	88.69% <100.00%> (+0.84%)	⬆️

[Flarna]

I think also that the problem here is the backend which seems to take data and just display it.
It seems elastic apm is aware that that it displays a http.statusCode which is known to be an integer therefore it should be no big deal to convert it.

Assume other attributes which are real doubles. They may be sent sometimes as int and sometimes as double now. This may result in similar issues as you see it now - just reversed.

[kudlatyamroth]

@Flarna thats why i check also with Number.isInteger which should eliminate problem with 1.32, as this will be send as double

[Flarna]

Consider an attribute some.probability where double values in range [0, 1] are used.
0 and 1 are sent as integer now and all the rest as double.

Therefore a receiver has to be prepared to get mixed data even with this change and a receiver has to need to convert data in some cases.

Anyhow, this shouldn't be seen as blocking.

[kudlatyamroth]

maybe use Decimal.js, if value is decimal.js always send as double?

[kudlatyamroth]

should i do anything else to have it merged?

if it will be merged, can you release fix version 0.17.1 ?