Document how to set up the plugin so that it does not break custom repository configuration

It would be helpful to document this approach. I've found it annoying that my project started complaining about all other dependencies which are usually fetched from a custom repository once I added this plugin.

// Append this to the bottom of your settings.gradle.kts
dependencyResolutionManagement {
  repositories {

    ivy {
      url = uri("https://nodejs.org/dist")
      patternLayout {
        artifact("v[revision]/[artifact]-v[revision]-[classifier].[ext]")
        artifact("v[revision]/[artifact]-v[revision].[ext]")
      }
 
      metadataSources {
        artifact()
      }
    
      content {
        includeGroup("org.nodejs")
      }
    }
  }
}

and

// Node configuration
node {
  version.set("xx.yy.zz")
  download.set(true)
  nodeProjectDir.set(file("${projectDir}/..."))
  distBaseUrl = null
}

Start from the settings.gradle.kts repository configuration and the Node configuration shown in the issue. Document this setup in the plugin's configuration guidance, including how to preserve custom repositories while resolving Node.js artifacts. Done means users can follow the documented approach without dependency resolution complaints.