feat: add mode-scoped dispatcher skills for cloud and 6.5lts

[abhishekgarg18]

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (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 change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[rombert]

Still learning about skills packaging, so only two high-level questions from me

• is it intended to have 'skills' twice in the path? ( e.g. skills/aem/cloud-service/skills/dispatcher )
• will the skills/aem/shared/reference/ files be resolved when only a subset of the skills are installed, e.g. npx skills add https://github.com/adobe/skills/tree/main/skills/aem/cloud-service/skills/dispatcher --all ?

[abhishekgarg18]

@rombert

1. Yes — that duplication is intentional and matches the existing EDS skill layout we followed for parity. The first skills/ is the repo-level grouping (the mono-repo’s top folder), while the second skills/ scopes the product/component subtree and contains the actual skill implementation. We kept this structure so the new skills remain consistent with existing repos and tool expectations; flattening it would break parity and make upgrades/migrations more error-prone.

2. Yes, you are right, these are not installed, we either have to create these as seprate skills (but that defeats the purpose, here), or make skills self contained, so i have made these self contained.

[abhishekgarg18]

updated the base to @beta branch

[rombert]

LGTM, thanks @abhishekgarg18 . Feel free to merge if ready (but please adjust the PR title :-) )