Is your feature request related to a problem? Please describe.
Current APM usage relies on collection.yaml to define a collection and apm.yml (at the repository root) to describe the collection’s contents. This makes it awkward to organize large repos as collections, and there is no supported way to place an apm.yml inside a subfolder that represents a “collection” or to reference apm.yml from another repository. As a result, reusing configurations across repos (and building MCP-style collections like Jira/Confluence) is hard, and the central format maintained by APM isn’t leveraged consistently for cross-repo references.

Describe the solution you'd like
Introduce an include mechanism to allow apm.yml (local or remote) to be referenced from within a collection (subfolder), so that apm.yml does not have to live only at repo root

/collections/backend-dotnet/apm.yml
or
/collections/backend-dotnet.apm.yml

Additional context
Benefits:

• Keeps a single, APM-maintained format while enabling cross-repo references and local sub-collections.
• Enables building MCP-style collections within the same structure (e.g., MCP for Jira/Confluence).
• Improves repository organization by allowing nested collections without requiring the creation of a new repository to have an apm.yml file at the root.