Revert YAML anchors approach - Dependabot doesn't support them

[Copilot]

Addresses a Dependabot parser limitation discovered when attempting to reduce duplication in .github/dependabot.yml.

Background

The original goal was to eliminate duplication where identical groups configuration was repeated across three npm package ecosystems. An attempt was made to use YAML anchors and aliases to define the configuration once and reuse it.

Issue Discovered

Dependabot's configuration parser does not support YAML anchors and aliases, despite them being valid YAML syntax. The parser raised the error: "YAML aliases are not supported"

Resolution

Reverted to the original configuration format where the groups configuration is explicitly duplicated across all three npm package ecosystems (root "/", "/dbg", and "/providers").

# Current approach: Groups duplicated across npm ecosystems
- package-ecosystem: "npm"
  directory: "/"
  groups:
    nevware21:
      patterns:
        - "@nevware21/*"
    # ... repeated for each ecosystem

- package-ecosystem: "npm"
  directory: "/dbg"
  groups:
    nevware21:
      patterns:
        - "@nevware21/*"
    # ... same configuration

- package-ecosystem: "npm"
  directory: "/providers"
  groups:
    nevware21:
      patterns:
        - "@nevware21/*"
    # ... same configuration

While this approach contains duplication, it's the only format that Dependabot's parser currently supports. Future changes to dependency grouping logic will need to be manually updated in all three locations.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[nev21]

Dependabot couldn't parse the config file at .github/dependabot.yml. The error raised was:

YAML aliases are not supported
Please ensure the config file is a valid YAML file. An online YAML linter is available here.

[Copilot]

Dependabot couldn't parse the config file at .github/dependabot.yml. The error raised was:

YAML aliases are not supported
...

I've reverted the YAML anchors approach in commit ae734a0. Unfortunately, Dependabot's parser doesn't support YAML anchors/aliases, even though they're part of the YAML specification. This is a known limitation of Dependabot's configuration parser.

The configuration is now back to the original format with the groups duplicated across the three npm ecosystems. While this means maintaining the same configuration in three places, it's the only approach that Dependabot currently supports.

If reducing duplication is still desired, the alternative would be to consolidate the three npm directories into a single monorepo structure, but that would require significant repository restructuring beyond the scope of this PR.