feat: Allow selector traits to be conditionally filtered

[mike-plummer]

Enabling selector traits to be conditionally filtered so that they can be included/excluded based on user-supplied config. The idea is that creating selectors based off id could be configured to ignore certain patterns of auto-generated values:

unique(
  el,
  {
    selectorTypes: ['id'],
    filters: {
      'id': (type, key, value) => {
        return !isAutoGeneratedValue(value)
      }
    }
  }
)

This filtering piggybacks on existing behavior in the selector generation logic to effectively pretend various traits (or portions of traits) just don't exist, thus can't be used when building selectors and automatically falling back to the next-highest-precedence trait.

The initial intent here is to support UICoverage user-supplied config to address auto-generated values breaking element de-duping. This will be primarily around attribute-based selector filters, but for completeness I've added support for filtering all selector types. Aggregate-style traits (class and attributes) allow filtering by part so that individual attribute names/values and classes can be filtered.

In addition, I've done some minor cleanup of attribute logic (using updated element APIs rather than iterating using older-style APIs).

[github-actions]

🎉 This PR is included in version 1.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀