[tests] Run yaml tests in groups if over 100 to run

[jesserockz]

What does this implement/fix?

Implements alternate CI jobs for when there are too many components to test.
For example, changing anything in the components/sensor folder will trigger every sensor platform, which then exceeds github workflow matrix limits. These new jobs will instead split the components into 20 random groups and test them in series there.

In theory this is actually faster as the framework and libraries only need to be download once per group, not once per component.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other

Related issue or feature (if applicable): fixes

Pull request in esphome-docs with documentation (if applicable): esphome/esphome-docs#

Test Environment

• ESP32
• ESP32 IDF
• ESP8266
• RP2040
• BK72xx
• RTL87xx

Example entry for config.yaml:

# Example config.yaml

Checklist:

• The code change is tested and works locally.
• Tests have been added to verify that the new code works (under tests/ folder).

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in esphome-docs.