feat: enabling the extraction of a specific selection from an element

[Azhovan]

What?

This pull request introduces enhancements to the k6 HTML module, including the addition of the Selection function. Its is designed to improve HTML parsing and manipulation capabilities within k6:

• Selection Method: Added to the Element type, it facilitates operations on the HTML content represented within an Element.

issue: #2683

Why?

• Addresses the need for a more intuitive API for DOM element selection and manipulation in performance testing scripts.

Checklist

• I have performed a self-review of my code.
• I have added tests for my changes.
• I have run linter locally (make lint) and all checks pass.
• I have run tests locally (make tests) and all tests pass.
• I have commented on my code, particularly in hard-to-understand areas.

Related PR(s)/Issue(s)

[CLAassistant]

All committers have signed the CLA.

[codecov-commenter]

Codecov Report

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

Comparison is base (7d131d6) 72.48% compared to head (6203dce) 72.47%.
Report is 13 commits behind head on master.

❗ Current head 6203dce differs from pull request most recent head 139495f. Consider uploading reports for the commit 139495f to get more accurate results

Files	Patch %	Lines
cmd/builtin_output_gen.go	16.66%	19 Missing and 1 partial ⚠️
cmd/report.go	63.41%	15 Missing ⚠️
execution/scheduler.go	57.57%	7 Missing and 7 partials ⚠️
js/modules/resolution.go	0.00%	5 Missing ⚠️
cmd/outputs.go	62.50%	2 Missing and 1 partial ⚠️
execution/controller.go	75.00%	1 Missing and 1 partial ⚠️
cmd/inspect.go	0.00%	1 Missing ⚠️
cmd/run.go	85.71%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3519      +/-   ##
==========================================
- Coverage   72.48%   72.47%   -0.01%     
==========================================
  Files         276      278       +2     
  Lines       20842    20933      +91     
==========================================
+ Hits        15108    15172      +64     
- Misses       4771     4786      +15     
- Partials      963      975      +12     

Flag	Coverage Δ
ubuntu	72.47% <56.42%> (+0.03%)	⬆️
windows	?

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.

[joanlopez]

It looks generally good, despite of the minor suggestions I left. However, after reading the discussion on the issue, I am not super confident about whether or not we want to expose/add (all) these methods. So, adding Mihail as reviewer, cause I've seen he's been involved in the discussion and so might have some feedback/thoughts to share around that.

Thanks!

[Azhovan]

what do you think @mstoykov about @joanlopez comment above

I am not super confident about whether or not we want to expose/add (all) these methods

[mstoykov]

I think Locator was just something @w1kman talked about, but shouldn't really be part of this fix at all.

The FromElement was based on the idea that Selection is the prototype that is implemented by each selection, and it will have a method (like static/moduled method in most other cases) and that will be used.

As we do not have currently a Selection prototype (AFAIK) - this isn't really possible.

As such I feel like we should just go with the selection method and drop everything else?

p.s. sorry I was away for the holidays and this then fell through the cracks 🙇

[mstoykov]

LGTM!

I kind of would prefer if the test was with teh original example, but not a big problem as long as it works.