Converts the list assessment to use the HTML parser

[mhkuu]

Context

• We want to rely less on regular expressions for our assessments. Therefore, we convert the list assessment to use the HTML Parser.

Summary

This PR can be summarized in the following changelog entry:

• Converts the list assessment to use the HTML parser.
• [yoastseo] Converts the list assessment to use the HTML parser.
• [shopify-seo] Converts the list assessment to use the HTML parser.

Relevant technical choices:

• None.

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

• See this document for testing instructions.

Relevant test scenarios

• Changes should be tested with the browser console open
• Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
• Changes should be tested on different editors (Default Block/Gutenberg/Classic/Elementor/other)
• Changes should be tested on different browsers
• Changes should be tested on multisite

Test instructions for QA when the code is in the RC

• QA should use the same steps as above.

QA can test this PR by following these steps:

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

• The list assessment.

UI changes

• This PR changes the UI in the plugin. I have added the 'UI change' label to this PR.

Other environments

• This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.

Documentation

• I have written documentation for this change. For example, comments in the Relevant technical choices, comments in the code, documentation on Confluence / shared Google Drive / Yoast developer portal, or other.

Quality assurance

• I have tested this code to the best of my abilities.
• During testing, I had activated all plugins that Yoast SEO provides integrations for.
• I have added unit tests to verify the code works as intended.
• If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
• I have written this PR in accordance with my team's definition of done.
• I have checked that the base branch is correctly set.

Innovation

• No innovation project is applicable for this PR.
• This PR falls under an innovation project. I have attached the innovation label.
• I have added my hours to the WBSO document.

Fixes https://github.com/Yoast/lingo-other-tasks/issues/172

[coveralls]

Pull Request Test Coverage Report for Build 63d0eb491ae49929262380332403fe2dde48f7e0

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 3 of 3 (100.0%) changed or added relevant lines in 1 file are covered.
• 81 unchanged lines in 2 files lost coverage.
• Overall coverage increased (+0.008%) to 54.591%

---

Files with Coverage Reduction	New Missed Lines	%
packages/js/src/general/app.js	11	0.0%
packages/js/src/first-time-configuration/first-time-configuration-steps.js	70	0.0%

Totals
Change from base Build e77fc968b8abc0e6e1080657a553383ebffc5eb4:	0.008%
Covered Lines:	29664
Relevant Lines:	54619

---

💛 - Coveralls

[FAMarfuaty]

In Shopify, I tested this PR together with this one https://github.com/Yoast/shopify-seo/pull/2017, since it's not merged yet. Otherwise Lists assessment is not available on product pages.

[FAMarfuaty]

CR and acceptance test: Everything works well, I tested both on Woo products and Shopify products. I pushed some additional commits to make sure that the assessment only counts non-empty lists. Further discussion on this approach can be seen in this Slack thread.