python3-boto3 and python3-botocore should be upgraded always together

[thomas-roos]

At the moment python3-boto3 and python3-botocore are in separate PRs when doing an nightly upgrade and this will cause one to fail. So rebase after the first is merged is required.
Tried so far

• common inc
• RECIPE_UPGRADE_EXTRA_TASKS

[rpcme]

Proposed solution

The most practical fix is in the auto-upgrader (meta-aws-ci/auto-upgrader/upgrader/updates.py):

Add a grouping map so that coupled recipes are detected and upgraded in a single branch/commit/PR:

UPGRADE_GROUPS = {
    "python3-boto3": ["python3-boto3", "python3-botocore", "python3-s3transfer"],
    "python3-botocore": ["python3-boto3", "python3-botocore", "python3-s3transfer"],
    "python3-s3transfer": ["python3-boto3", "python3-botocore", "python3-s3transfer"],
}

When any recipe in the group is found to be upgradable, upgrade all members together on a single branch with a combined commit. This avoids the rebase-after-first-merge problem entirely.

~20 lines of changes to updates.py. Does not depend on upstream OE-core grouping support (which was tried via RECIPE_UPGRADE_EXTRA_TASKS without success).