Plugin Dependencies Include `test` Scope

[adambkaplan]

I'm testing maven-lockfile-plugin v5.11.0 (thank you, by the way!) on a real world project (https://github.com/kserve/modelmesh), and noticed with the new version, the plugin dependency tree includes test scoped dependencies:

  "mavenPlugins": [
    {
      "groupId": "org.apache.maven.plugins",
      "artifactId": "maven-jar-plugin",
      "version": "3.1.2",
      "checksumAlgorithm": "SHA-256",
      "checksum": "1604783d702ab50adecea6ed539f76bf158b179131cc6e2786185e8af08b08e2",
      "resolved": "https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-jar-plugin/3.1.2/maven-jar-plugin-3.1.2.jar",
      "repositoryId": "central",
      "dependencies": [
        {
          "groupId": "junit",
          "artifactId": "junit",
          "version": "4.12",
          "checksumAlgorithm": "SHA-256",
          "checksum": "59721f0805e223d84b90677887d9ff567dc534d7c502ca903c0c2b17f05c116a",
          "scope": "test",
          "resolved": "https://repo.maven.apache.org/maven2/junit/junit/4.12/junit-4.12.jar",
          "repositoryId": "central",
          "selectedVersion": "4.12",
          "included": true,
          "id": "junit:junit:4.12",
...

Is this sort of behavior desired? I suspect test dependencies of plugins are not downloaded when Maven resolves them, but I could be wrong here.