Add Scan method for ResultSet to scan the rows into the given slice (Part 1)

[haoxins]

What type of PR is this?

• bug
• feature
• enhancement

What problem(s) does this PR solve?

Issue(s) number:

#296

Description:

This PR includes changes in #297,
I add the first draft implementation for the API proposed in #296.

Some tasks need to be done, such as

• Support all the fundamental types;
• Support nest structure type;
• Add more tests.

But I raised this PR as a draft in case there are some potential concerns from your guys.
So feel free to leave some comments here.

Such as can we drop support for Go versions that < 1.18?

cc @wey-gu @veezhang

How do you solve it?

Special notes for your reviewer, ex. impact of this fix, design document, etc:

[haoxins]

@wey-gu @veezhang Any thoughts?

[Nicole00]

some ci failures need to be deal due to the go version.

[haoxins]

some ci failures need to be deal due to the go version.

@Nicole00 may I just removed the go versions <1.18?

[codecov-commenter]

Codecov Report

Attention: 23 lines in your changes are missing coverage. Please review.

Comparison is base (6eb07e9) 63.41% compared to head (fd13b92) 63.37%.

Files	Patch %	Lines
result_set.go	57.40%	18 Missing and 5 partials ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #298      +/-   ##
==========================================
- Coverage   63.41%   63.37%   -0.05%     
==========================================
  Files           8        9       +1     
  Lines        2392     2452      +60     
==========================================
+ Hits         1517     1554      +37     
- Misses        750      768      +18     
- Partials      125      130       +5     

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

[Nicole00]

some ci failures need to be deal due to the go version.

@Nicole00 may I just removed the go versions <1.18?

For now we can't remove the go version yet. Because it will confluence the users' usage when upgrade the nebula-go.

[haoxins]

some ci failures need to be deal due to the go version.

@Nicole00 may I just removed the go versions <1.18?

For now we can't remove the go version yet. Because it will confluence the users' usage when upgrade the nebula-go.

ok, I will remove the usage of lo which requires Go 1.18+

[haoxins]

some ci failures need to be deal due to the go version.

@Nicole00 may I just removed the go versions <1.18?

For now we can't remove the go version yet. Because it will confluence the users' usage when upgrade the nebula-go.

@Nicole00 I have added the Go 1.16+ back

[haoxins]

@Nicole00 any other comments?