JobGroups check active job to determine if in progress

[mdegat01]

Proposed change

Descendents of Job Groups do not use a a lock member on the class to track whether a task is in progress, they ask the job group if there's an active job. This currently creates issues like JobGroupExecutionLimitExceeded: Another job is running for job group container_hassio_observer from plugin watchdog as it does not know another job is already happening.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (which adds functionality to the supervisor)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:
• Link to cli pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast supervisor tests)
• Tests have been added to verify that the new code works.

If API endpoints of add-on configuration are added/changed:

• Documentation added/updated for developers.home-assistant.io

[agners]

I see, with this change we can learn if a job is in progress and handle this cases more gracefully, so the exceptions don't show up anymore. Nice catch!