feat(collection): add task split

[chuang8511]

Because

• it make pipeline easier to manipulate array

This commit

• add task split

[linear]

INS-6641 Collection: Task Split

[codecov]

Codecov Report

Attention: Patch coverage is 90.00000% with 2 lines in your changes missing coverage. Please review.

Project coverage is 19.58%. Comparing base (f956ead) to head (292bf32).
Report is 15 commits behind head on main.

Files with missing lines	Patch %	Lines
pkg/component/generic/collection/v0/main.go	90.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #780      +/-   ##
==========================================
- Coverage   19.70%   19.58%   -0.12%     
==========================================
  Files         321      322       +1     
  Lines       64847    65458     +611     
==========================================
+ Hits        12776    12819      +43     
- Misses      50162    50726     +564     
- Partials     1909     1913       +4     

Flag	Coverage Δ
unittests	19.58% <90.00%> (-0.12%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[GeorgeWilliamStrong]

From document perspective, LGTM

[pinglin]

@chuang8511 Can we separate all tasks into task_* like what the Image operator has done? I found it's getting harder and harder to trace code in a single file across so many components and tasks. cc'd @donch1989 @jvallesm

[jvallesm]

@chuang8511 Can we separate all tasks into task_* like what the Image operator has done? I found it's getting harder and harder to trace code in a single file across so many components and tasks. cc'd @donch1989 @jvallesm

@pinglin do you mean in this case or as a convention?

To me it depends on the size of the main.go file. When we start a component and we have 1-2 (simple) tasks, I find it beneficial to have everything in a single file vs having several small files. As the component code grows, it makes sense to me to start dividing the logic into files.

But it isn't a strongly-held opinion, I could do with a convention, too.

[chuang8511]

@chuang8511 Can we separate all tasks into task_* like what the Image operator has done? I found it's getting harder and harder to trace code in a single file across so many components and tasks. cc'd @donch1989 @jvallesm

Updated.
And, change to ConcurrentExecutor