feat: respect iox::column_type::field metadata when mapping query results into values

[bednar]

Closes https://github.com/influxdata/EAR/issues/5646

Proposed Changes

1/ This PR changed how we parse response from InfluxDB, now we respect the iox::column_type::field metadata.
2/ Enhance documentation for Query API.

Checklist

• CHANGELOG.md updated
• Rebased/mergeable
• A test has been added if appropriate
• Tests pass
• Commit messages are conventional
• Sign CLA (if not already signed)

[codecov]

Codecov Report

Attention: Patch coverage is 73.33333% with 24 lines in your changes missing coverage. Please review.

Project coverage is 88.03%. Comparing base (c805bae) to head (bc28c61).
Report is 3 commits behind head on main.

Files with missing lines	Patch %	Lines
influxdb3/query_iterator.go	73.33%	24 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #114      +/-   ##
==========================================
+ Coverage   87.60%   88.03%   +0.42%     
==========================================
  Files          15       15              
  Lines        1299     1337      +38     
==========================================
+ Hits         1138     1177      +39     
  Misses        134      134              
+ Partials       27       26       -1     

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

[jstirnaman]

Thanks for alerting me!

[bednar]

@jstirnaman thanks for you review! All is done.

[vlastahajek]

Generally, it looks good.
However, I would recommend changing interface{} to any

[bednar]

Thx @vlastahajek, the interface{} is changed to any.

[karel-rehor]

Looks good.

[bednar]

@karel-rehor, @vlastahajek, could you please review this PR again? I’ve updated the major version of the client and the base "package".

[karel-rehor]

Tests pass locally. All examples work for me. Changes make sense. Looks good.

[vlastahajek]

What do you think about providing a utility function for backward compatibility?

[bednar]

@vlastahajek, could you clarify what the function for backward compatibility will do? Will it be a helper to translate time.Time to arrow.Timestamp?

[vlastahajek]

Change interface{} -> any here and elsewhere?

[vlastahajek]

@vlastahajek, could you clarify what the function for backward compatibility will do? Will it be a helper to translate time.Time to arrow.Timestamp?

If it makes sense at all, either a function(s) that would convert the new output to the previous form for the output methods Value and AdPoints().

[bednar]

@vlastahajek, could you clarify what the function for backward compatibility will do? Will it be a helper to translate time.Time to arrow.Timestamp?

If it makes sense at all, either a function(s) that would convert the new output to the previous form for the output methods Value and AdPoints().

I don’t think that’s necessary. The changes involve the types of return objects. Previously, they were from the arrow package, but now they are GoLang types, which are more convenient for users and easier to use.