#7684: adds error details for multiple selectors and no selectors found errors

[grahamlangford]

What does this PR do?

• Closes Report selector in error detail in Page Editor #7684

Discussion

• Currently have the Multiple and No Elements Found Detail views as duplicated files in case we want to change the styling between the two in any way.
• Will combine into a single Detail component if we're happy to keep the designs the same for each.

Demo

https://www.loom.com/share/3838c3b3bf644851bae7266df3f68b32

Checklist

• Add tests
• New files added to src/tsconfig.strictNullChecks.json (if possible)
• Designate a primary reviewer @twschiller

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.14%. Comparing base (19ea4eb) to head (a3aecd2).

❗ Current head a3aecd2 differs from pull request most recent head 384cfd8. Consider uploading reports for the commit 384cfd8 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7752   +/-   ##
=======================================
  Coverage   72.13%   72.14%           
=======================================
  Files        1268     1269    +1     
  Lines       39753    39765   +12     
  Branches     7373     7375    +2     
=======================================
+ Hits        28676    28687   +11     
- Misses      11077    11078    +1     

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

[twschiller]

Seems like you could use a single component that takes either a MultipleElementsFoundError or NoElementsFoundError because you're relying on the same property?

[grahamlangford]

Agreed. I should've opened this as a draft and called it out. I kept them separate in case there were any design concerns where they would end up different.

[twschiller]

See comment on reusing the error detail component: https://github.com/pixiebrix/pixiebrix-extension/pull/7752/files#r1506105859

[github-actions]

When the PR is merged, the first loom link found on this PR will be posted to #sprint-demo on Slack. Do not edit this comment manually.

[BrandonPxBx]

Discussed with @grahamlangford

We should take a more holistic look at error messaging at a later date