Support for plugin header "Requires Plugins" to simplify blueprints

Would be great if the blueprints library would support the newly introduced plugin header "Requires Plugins" that was introduced in WP 6.5 (https://make.wordpress.org/core/2024/03/05/introducing-plugin-dependencies-in-wordpress-6-5/).

This would then simplify the blueprints needed to create a WP install for a plugin that require other plugins to work. Eg as for the example mentioned in the blog post, https://wordpress.org/plugins/wpsso-wc-metadata/, you would only have to have a blueprint like:

{
  "preferredVersions": {
    "php": "8.0",
    "wp": "latest"
  },
  "phpExtensionBundles": [
    "kitchen-sink"
  ],
  "plugins": [
    "wpsso-wc-metadata"
  ],
  "steps": [
    {
      "step": "login",
      "username": "admin",
      "password": "password"
    }
  ]
}

instead of:

{
  "preferredVersions": {
    "php": "8.0",
    "wp": "latest"
  },
  "phpExtensionBundles": [
    "kitchen-sink"
  ],
  "plugins": [
    "woocommerce",
    "wpsso",
    "wpsso-wc-metadata"
  ],
  "steps": [
    {
      "step": "login",
      "username": "admin",
      "password": "password"
    }
  ]
}

Start with the WordPress 6.5 plugin-dependencies reference and compare the two blueprint examples in the issue. Determine how the blueprints library should use the “Requires Plugins” header so the shorter blueprint installs its dependencies, and verify that behavior with coverage in the relevant existing tests.